Open jakub-g opened 9 years ago
Ah, well, it's once again the caching issue.
I looked up ~/.config/browser-launcher2/config.json
and it contained Canary entry, apart from regular Chrome entry, and somehow the tool decided to use Canary instead of stable in this case.
Deleted it, and now the file was recreated but without Canary entry.
I will need to dig further to understand what's going on.
Windows 7 64-bit, node 0.10.40 / 0.12.7, Chrome stable (45) and Canary (47) installed
When I run the following code:
the output is
(it detects Chrome stable)
But then, Chrome Canary windows pops out on screen.
So it seems that detection logic and launch logic is different