Tools: Firefox always opens First Run page instead of tests

[JohnRiv]

For me on OSX, starting with Firefox v43.0.1, whenever I run WCT, it opens up https://www.mozilla.org/en-US/firefox/43.0.1/firstrun/learnmore/ instead of the tests. Same thing happened with v43.0.2 (except the URL is of course https://www.mozilla.org/en-US/firefox/43.0.2/firstrun/learnmore/).

I've tried forcing configuration options on Firefox, but those do not take effect when WCT runs FF for some reason (I confirmed by checking about:config when running $ wct -p)

According to these StackOverflow questions below, it appears it's possible to programatically create a Firefox profile for Selenium/WebDriver to use, but I'm unsure how I can configure this with WCT or if there's a better way to handle it:

• Firefox webdriver opens first run page all the time
• FirefoxDriver always starting on “firstrun” page, breaking all test scripts

Any ideas?

[andyfinity]

Downgrading to Firefox v41.0.1 worked for me.

[JohnRiv]

Cool that works for me too. Thanks, I can run tests again.

[TimvdLippe]

/sub

[sandro-k]

+1

[ckuiawa]

Awesome! So the solution is to downgrade my evergreen browser. That is fantastic! (By the way, downgrading worked for me. But what the heck?)

[gjdenhertog]

After a little bit of fiddling around I suspect that the issue is based off the fact that selenium starts Firefox with a anonymous profile. This profile has the preference "startup.homepage_welcome_url.additional" set to the https://www.mozilla.org/nl/firefox/43.0.1/firstrun/learnmore/ url. I'm still figuring out if it is possible to update this preference from selenium.

Update: I stand corrected the issue seems to be that Firefox is unable to connect to the localhost server.

[justinfagnani]

@JohnRiv sorry about the delayed response. I set this to high priority, but may be critical depending on how bad the impact is and ugly workarounds are.

Does anyone know if there's a command line flag in Firefox to suppress the learn more page? If so, we could easily add that, otherwise we have to look into creating a profile...

[justinfagnani]

Maybe we could ship a profile as in: https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options#-profile_.22.2Fpath.2Fto.2Fprofile.22

The note about relative paths on OS X is ominous though.

[TimvdLippe]

@justinfagnani Could you please update the priority of this issue to critical? This problem causes wct to be unusable on the command line if FireFox is installed.

[TimvdLippe]

My Firefox was updated to Firefox 46 and it is working once again :tada:

[justinfagnani]

wow, that's awesome, because I hadn't found a good solution!

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.