On 2/7/2015 4:38 AM, Jet Villegas wrote:
We should pick this up too.
I'm skeptical of the immediate value. We need to focus on Flash hangs and also the security issues surrounding Flash 0-days especially as distributed by ad networks. Power saving is not our immediate or medium-term focus.
It seems that this proposal focuses on authors opting in, and providing a better experience for per-element click-to-play behavior. What fraction of existing Flash has a usable poster? By adopting this proposal, would we also be adopting a per-element click-to-play approach? If so, is this for all 3rd-party Flash, or just for known advertising sites, or for all Flash? User studies have shown that typically users won't understand the difference between Flash and the browser, and the "extra click" isn't a usable solution for most people. If we can be confident of limiting this to advertising, that evaluation might change (because users are used to clicking on advertising already).
Note that if we're talking about something other than poster attributes, I have more serious concerns: the differences between windowed and windowless Flash are significant, and our control over windowed Flash is pretty minimal. In order to do automatic posterization the way Safari does it, we'd need to ensure that the elements are windowless, *or* we'd need to invent a pretty complex mechanism for control over windowed Flash and taking snapshots of windows.
I'd encourage somebody to implement this as an addon or behind a hidden pref, and see what the experience is like and whether users like it. It should be possible to implement this as an addon.
--BDS _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
