To enable this feature, we need to figure out a UI notification mechanism that allows the user to understand persistently permitted/denied permissions. An 'allows block plugins on this site' options could leave a site broken and confuse the user.UX - Invisible (or barely visible) plugins will cause an infobar to appear to enable all plugins on the page - how do we handle multiple invisible (or barely visible) plugins on a page ? (stacking infobars ?).What warnings show up when a user wants to enable an out of date plugin? What does the UX of the 'scary warning' look like? Do we direct users to the plugin check website as part of the warning? Do we have two levels of warnings (scary and really scary) and what would they look like?.Where are the preferences to require click to play for all or specific plugins? Where are the preferences to have separate plugin permissions per-site?.What type of UX to have for allowing users to opt in (or out) of enabling plugins on a (semi)persistent basis? See below in 'Use Cases'.This will be determined later on, after some of the phases land.Can content differentiate between 'click to play' and 'hard-disabled for security reasons'?.Pandora) so that they can show alternate UI (plugins are disabled, please click to play) instead of timing out and showing a generic 'please install Flash' or 'Song initialization timed out, please hit refresh' UI.'

Bsmedberg asks in bug 711552: 'Are we exposing to the DOM that a particular plugin element ( or is user-disabled?) This seems important for websites that rely primarily on plugins (e.g.Adverse reactions between content plugin sniffing and click-to-play.Initial minimal implementation landed for 14 (opt-in), further work in 15 and 16. Please use 'Edit with form' above to edit this page.

Firefox flash plugin always activate