Firefox disables shockwave flash plugin option to "Never Active" and "Block dangerous and intrusive Flash content" option is selected while running scripts through selenium webdriver. Because of it, unable to click on Flash objects.
I have tried below options but didn't work for me.
3. I tried changing all the possible combinations of
Still when my script is running, Shockwave Flash is set to "Never Activate" in Firefox quantum browser(Version:60.0) but same issue is not noticed in older versions of FireFox broswer(version:46).
Please provide solution to set shockwave Flash plugin to "Always Activate".
Title edited for brevity by moderator. Was:"While Automating Websites through Selenium, FireFox(Version:60) is Disabling Shockwave Flash ( version 29.0) player because of it Flash Objects cannot be clicked while running scripts. Please provide us solution to always enable flash player ."
meanwhile you can also contact firefox developers and post your issue there.
This is a browser issue, not Flash Player issue. The browser is the one that controls when to load the plugin, not Flash Player. Please contact Firefox for assistance.
I tried contacting Firefox developers, but i did not receive any help. so i posted the issue here also.
did you try with other browsers like opera, edge?
I need to run my scripts on latest Firefox browser only!.
Unfortunately, this is the browser imposing restrictions in the normal operation of Flash Player. The solution needs to come from the browser.
You might have some luck playing with options in about:config.
plugins.flashBlock.enabled seems promising, but Mozilla would be the authoritative source.
Yes i tried with all the option of Config properties, but still Mozilla blocks the Flash player.
Have you tried this?
Short of that, I don't have any great suggestions.
Either your testing requirements will need to change to accommodate the constraint (e.g. just pin your testbed to the last version of Firefox that allowed you to keep Flash enabled), or you'll need to change to a more flexible automation tool which can interact with the browser's security dialogs (e.g. Sikuli).
I guess there's a third option, since Firefox is Open Source. You could build your own Firefox with a patch that disables the click to activate plug-ins feature, but that seems pretty painful, and you'd have to integrate the patch every time you want to build....