FIREFOX FLASH PLUGIN ALWAYS ACTIVATE CODE
FIREFOX FLASH PLUGIN ALWAYS ACTIVATE FREE

FIREFOX FLASH PLUGIN ALWAYS ACTIVATE CODE

What that code does is if you simply click 'allow' it will set a session scoped permission to allow Flash. Yeah, so, the plugin permissions in the doorhanger are set here:

do existing users get this change applied, and/or do we need to notify them in any way beyond relnotes?Īll users should get this change.

The flash_only pref should only be used for our automated NPAPI tests, so we can disable or remove the pref in non-test code paths, as long as disabling it doesn't affect Widevine or OpenH264. Widevine and OpenH264 are also 'plugins' but we do not want to remove their always-allow support.

can we remove support for the flash_only pref except when running automated tests (to reduce the testing/complexity matrix), or is that not possible at the moment?įlash and the dummy NPAPI test plugin are the only NPAPI plugins we support.

we still have a flash_only pref that allows other plugins to be used - in this bug, do we just want to remove support for 'always run' for all plugins?.

Chrome has shipped a similar always-ask UX since September 2018, so there should not be any Flash sites that cause problems in Firefox but not Chrome:

do we need a pref to turn off this restriction if we uncover too many issues?.

However, we do not want to remove always-run support for the dummy NPAPI test plugin (used for our automated NPAPI tests), Widevine, or OpenH264! Widevine and OpenH264 are GMPs (Gecko Media Plugins), not NPAPI plugins, so they might use a different code path. :) We'll also need to remove any Flash code in the Site Permissions UI. If there are Flash issues, we want to find them during Nightly testing, not 90 days from now.

But we should probably remove Gecko's always-run Flash code (somewhere in dom/plugins/base) now so Firefox Nightly users can actually experience the always-ask Flash UX now. We had planned to just remove the UI to prevent setting new always-allow site permissions and then let users' existing always-allow site permissions quietly expire after 90 days.

I'm assuming we want to actually make this completely impossible, not just remove the UI and keep support for the internal 'always run this plugin' state?.

No, but I'll create a doc that consolidates all these answers:

Is there a broader plan for what we want here? Some questions that spring to mind (which perhaps are answered in such a doc somewhere):

Therefore, you need to activate it on sites you trust to use it instead of being able to set Firefox to let all sites use Flash automatically.(In reply to :Gijs (he/him) from comment #4) Read this answer in context 👍 6 All Replies (7)ĭue to a confessed vulnerability in Adobe's current version (), Mozilla has soft-blocked the latest version of the Shockwave Flash plugin.

FIREFOX FLASH PLUGIN ALWAYS ACTIVATE FREE

If you don't see an immediate need for Flash, feel free to ignore the notification, it will just sit there in case you want it later. Your choice: for the current usage, or permanent.īut the page might be using Flash only for tracking or playing a video ad. If you see a good reason to use Flash, and the site looks trustworthy, you can go ahead and click the Lego-like icon in the address bar to allow Flash. When you visit a site that wants to use the Flash, you should see a notification icon in the address bar and one of the following: a link in a black rectangle in the page or an infobar sliding down between the toolbar area and the page. If you are not accustomed to using the 'Ask to Activate' feature for a plugin, here's what to expect:

Therefore, you need to activate it on sites you trust to use it instead of being able to set Firefox to let all sites use Flash automatically. Due to a confessed vulnerability in Adobe's current version ( ), Mozilla has soft-blocked the latest version of the Shockwave Flash plugin.

Firefox flash plugin always activate