Open matthew-dean opened 6 years ago
Not sure if this is a backstop issue or a puppeteer issue. Can you try this with a vanilla puppeteer script?
We're using Chromy. What do you mean by vanilla script?
Oh ok. Then what I mean is to..
1 make a temp directory somewhere.
2 Install chromy into that directory.
3 Creat a script that should open a few pages (as opposed to tabs) and see if it works as expected (when setting a chrome path.)
That should tell you if it's a chromy behavior or it's something that backstop is doing.
You could also just go to the chromy repo and pose the question there. See what they say.
When setting an explicit
chromePath
option, if you have a Chrome browser open (with an entirely different Chrome executable), Backstop will open numerous tabs with URLs likechrome-extension://gnhhdgbaldcilmgcpfddgdbkhjohddkj/devtools/inspector.html?ws=localhost:9229/devtools/page/65EA1DD450CFAEADD0B2C98DDCEAE5F3
in the active Chrome browser, instead of within the (headless, invisible) executable set inchromePath
.This wasn't happening before we set an explicit
chromePath
executable.