Mozilla may make Flash click-to-play by default in future Firefox
arstechnica.com
arstechnica.com
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, 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.
Minus a couple of restrictions (i.e. with CORS you cannot rely on cookies being set, so you need to handle that from your Javascript somehow), CORS works well and it works on all major browsers, starting with IExplorer 8, which makes it awesome.
Works great.
Preferences > Under the Hood > Privacy > Content Settings > Plug-ins > Click to play
Or you can search for "Flash" or "Click to play" to find the setting.
Clicking the puzzle piece shows a menu to "always allow" or to "enable all Flash applets on this page" (and a few other things).
I can see a more obtrusive/apparent UI being implemented if Firefox makes click-to-Flash default.
This was my entire point in the first place, if you look up at the beginning of the thread. For example, turn on click-to-play and then go to pandora.com. If Chrome treated Flash the same as Java, you would still be able to use pandora easily.
If Firefox requires 'click-to-play' on an on-screen piece of Flash to enable it, all sites using jPlayer to play mp3 simply will not work.
And of course this doesn't just affect jPlayer, many other players use this technique.
Much better -- as mistercow reasons -- to have a pop-up asking you if you wish to run Flash on a particular site and I would love to see an 'always allow' option here.
Let's please try to explain things instead of just downvoting questions.
Try this link http://forums.mozillazine.org/viewtopic.php?f=23&t=21175...
TL;DR there is a licensing issue with the MP3 decoder. It's more complicated than that, but most of it is due to software patents. http://en.m.wikipedia.org/wiki/MP3#section_10 has more info if you're curious.
Not if you whitelist it at Tools > Add-ons > Extensions > Flashblock > Preferences.
... cross-domain XHR
That's not a problem because Firefox has support for CORS, which is better than doing Flash because it's faster.Of course, the server must cooperate with the browser by passing back allowance headers, but that's also true for Flash, as you need the server to have a crossdomain policy file for that.
Last year I wrote an article about it on my blog about how to configure it, check it out: http://bionicspirit.com/blog/2011/03/24/cross-domain-request...
That's nice for a new site being developed right now, it's problematic for a site which has been stable in production for months or years and for which everybody involved in the development has moved on already.
Any effort to make the browser experience smoother is a good thing!
It was something to do with an "ActiveX control," I don't remember anymore. But you should have seen how angry it made 13-year-old-me, because my loud, annoying Flash creations had to be allowed their obnoxiousness by every user. Anyway, the point is I approve. :)
* I'm pretty sure it was IE, could be remembering wrong.
I think I ended up using something like this to bypass it: http://www.flashperfection.com/tutorials/Flash-ActiveX-Micro...
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.
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?
I might be ok with a timeout - after 30 seconds of no
interaction from me, suspend the tab. Would that address
your objection?
There has been experiments to do that (https://bugzilla.mozilla.org/show_bug.cgi?id=675539), and an (experimental) extension brings you this behavior (https://addons.mozilla.org/en-US/firefox/addon/dormancy/), but hasn't been updated in a while.Actually, this completely unloads the page from memory, which is not exactly what you ask for.
https://groups.google.com/d/topic/mozilla.dev.platform/jFAOP...
Flash files are worth silencing by default because you don't usually come to the website for them. They're largely unwanted web rodents.
Flash have just finally got (after like a hundred years) the ability to stay in full screen even if you focus another window.
Also, that will break all instant-messaging implementations - at least until you refocus that window. Imagine having to focus a window just to see whether the content has updated?
Not sure if that's feasible in firefox.
I see the setting in FF12b5 but not sure if it works yet.
[I'm a developer of Firefox for Android, which has click-to-play enabled by default starting with version 14.]
The world would be a better place without these two Adobe products. Their /content production/ software is amazing, and they should just stick to that IMO.
Sometimes this button is necessary if there's a 1x1 flash embed somewhere that is required for the page.
if there is some audio or video designated to play onLoad, notify user and have them click ok/prevent/mute...etc. it might make for some no-so-seamless experiences, but the alternative it 90's style animated gif annoyances on spam sites etc..
Not automatically loading java would be a great benefit to the majority of users. Its not used on nearly as many websites yet it is responsible for the lion's share of current security exploits.
http://www.computerworld.com/s/article/9046245/Microsoft_dro...
Turns out Microsoft did it because of patent issues.
In my opinion, there should always be a configuration option associated to a new feature/behavior like this!
Because in the end that's why I still use Firefox : I can configure it like I want!
Animated ads are the second most annoying thing on the web after embedded background music.
Again, don't blame the tools; blame the tools who use them.
I don't want anything on a web site animating or making noise without my specific permission.
I hope they don't turn it on, or advertisers will move away from Flash to Canvas.