When Flash is set as click-to-activate for a site: WHEN an <object> with Flash type has fallback content AND WHEN that fallback content does not heuristically match an "install Flash" message AND WHEN the fallback content is not a single <embed> element. THEN Render the page with the fallback content instead of showing the Flash click-to-play message Heuristic details, subject to validation: If the fallback content contains the words "install" and "Flash", in common languages, then it is a install-Flash message. If the fallback content contains a link to anywhere within adobe.com, it is an install-Flash message. This behavior must be instituted behind a feature pref. While we still support other plugins, this change must not affect the use of any other plugin.
We'd like to build a mode of Firefox execution where Flash is still available but is not used by default. This bug changes the order that we choose to run code in an <object> tag.
Since this bug contains the user story, I made it into a meta bug and filed all the relevant implementation bugs blocking this one.
I want to mention to other bugs that are not directly related to this but are worth watching (they are related to the existing URL-based blocking): bug 1277876 and bug 1268120
Please be sure to advise the docs team about any bugs related to this that will be of interest to web developers. I did not document the Flash hidden from navigator.plugins since it’s disabled by default now and things are up in the air on that, but be sure to put dev-doc-needed keyword on any bugs which are dev-facing. Thanks!
(Removing these bugs from the meta because they're already part of the dependency tree through bug 1282484