Again, don't blame the tools; blame the tools who use them.
Mozilla may make Flash click-to-play by default in future Firefox
11–20 of 121 posts
Re: Mozilla may make Flash click-to-play by default in future Firefox
#12Re: Mozilla may make Flash click-to-play by default in future Firefox
#13Re: Mozilla may make Flash click-to-play by default in future Firefox
#14Non-foreground tabs should be completely suspended - plugins, JavaScript, media, you name it - unless they specifically request and are granted permission to run in the background.
Re: Mozilla may make Flash click-to-play by default in future Firefox
#15In the short term, this will probably cause some breakage in certain sites that try to use Flash "transparently" and "unobtrusively" for things like LSOs, drag-and-drop, clipboard access, or cross-domain XHR. These are already problematic with Flashblock installed though -- Pandora, for instance, refuses to load and there is nothing available to click-to-play since that particular Flash object is hidden.
Hopefully this will light a fire under those sites and get them to update to the appropriate HTML5 methods of doing these things (local storage, WebSockets, etc.), just like how Java applets that were used for such things have been largely phased out. Until then, however, I wouldn't be surprised if some of them simply inform you not to use Firefox to visit.
Re: Mozilla may make Flash click-to-play by default in future Firefox
#16This is great, really, but I'd like to see something more aggressive: Non-foreground tabs should be completely suspended - plugins, JavaScript, media, you name it - unless they specifically request and are granted permission to run in the background.
setTimout and friends are throttled (at least in Firefox) to fire at most once every second, so you won't burn your battery having a graphic demo in the background.
Re: Mozilla may make Flash click-to-play by default in future Firefox
#17Re: Mozilla may make Flash click-to-play by default in future Firefox
#18I am so happy that I can barely contain myself. Hopefully this means Flash will now be used for important things, instead of shoving ads in my face that I can't dismiss, and follow my scroll bar.
You say that now, but just wait until they're written in JS+Canvas and enormously more difficult to block.
Re: Mozilla may make Flash click-to-play by default in future Firefox
#19This is great, really, but I'd like to see something more aggressive: Non-foreground tabs should be completely suspended - plugins, JavaScript, media, you name it - unless they specifically request and are granted permission to run in the background.
Quite a lot of webpages need js to initialize themselves, these days, and I want them to load in background when I middleclick on a link. You probably want (at least some) websites to perform XHR when not focused (to update a news stream or something). I find an opt-in behavior on such a common feature a bit to hard, as a lot of website rely on that. setTimout and friends are throttled (at least in Firefox) to fire a…
I run with JavaScript and Cookies disabled unless white-listed, and just leave the majority of pages that won't load. Techcrunch, Engadget, and most news sites are so much faster without JS.
I might be ok with a timeout - after 30 seconds of no interaction from me, suspend the tab. Would that address your objection?
Re: Mozilla may make Flash click-to-play by default in future Firefox
#20I welcome this move, despite the possibility of some fallout from the change. It'll be painful, but even as someone who once made a living writing ActionScript, I have to say that Flash is sufficiently annoying and insecure that it really needs to be phased out. In the short term, this will probably cause some breakage in certain sites that try to use Flash "transparently" and "unobtrusively" for things like LSOs, dr…