Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Learn More

Denna tråd har arkiverats. Ställ en ny fråga om du behöver hjälp.

Firefox Developer Edition shows popup that breaks Selenium script

  • 1 svar
  • 1 har detta problem
  • 5 visningar
  • Senaste svar av Standard8

funTeacher
funTeacher
more options

I'm trying to use Firefox Developer Edition (50.0a2 (2016-08-23)). When it opens, a small popup message appears saying: 

 Accessibility support is partially disabled due to
 compatibility issues with new Firefox Developer 
 Edition features.  
    Learn more....

and an OK button.

This popup breaks my Selenium webdriver scripts. How can I turn it off? Search of web says, just restart and it will start in single mode. But this doesn't work from inside the Selenium script. How can I start Firefox Developer in single mode the first time?

I'm trying to use Firefox Developer Edition (50.0a2 (2016-08-23)). When it opens, a small popup message appears saying: Accessibility support is partially disabled due to compatibility issues with new Firefox Developer Edition features. Learn more.... and an OK button. This popup breaks my Selenium webdriver scripts. How can I turn it off? Search of web says, just restart and it will start in single mode. But this doesn't work from inside the Selenium script. How can I start Firefox Developer in single mode the first time?

Alla svar (1)

Standard8
Standard8
more options

I've just had a dig around in the code. The message is prompted when the browser starts in the new-ish multiprocess mode.

It looks like you can avoid the message by setting the preference "browser.tabs.remote.force-enable" to true using selenium. That will force multiprocess on all the time, which is where Firefox is going, so it will be good for testing.