Mozilla may make Flash click-to-play by default in future Firefox
61–70 of 121 posts
Re: Mozilla may make Flash click-to-play by default in future Firefox
#62For my money, they oughta make Canvas click-to-play as well, since the rendering speed in Firefox is unbelievably slow and the javascript behind it is so frequently written to hog up 100% of the CPU it's hard to even know what you're looking at if you accidentally stumble across an HTML5 page in Firefox, before your system grinds to a complete halt. It's funny how people blame Flash for slow websites when what they s…
Re: Mozilla may make Flash click-to-play by default in future Firefox
#63I 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…
Not if you whitelist it at Tools > Add-ons > Extensions > Flashblock > Preferences.
Re: Mozilla may make Flash click-to-play by default in future Firefox
#64Didn't IE try this and developers got around it by using Javascript to embed flash? http://www.computerworld.com/s/article/9046245/Microsoft_dro... Turns out Microsoft did it because of patent issues.
Re: Mozilla may make Flash click-to-play by default in future Firefox
#65Didn't IE try this and developers got around it by using Javascript to embed flash? http://www.computerworld.com/s/article/9046245/Microsoft_dro... Turns out Microsoft did it because of patent issues.
The plug-in was still loaded and executed. It is just the interaction with the plug-in that required an extra click.
Re: Mozilla may make Flash click-to-play by default in future Firefox
#66Here's another suggestion: how about an invisible "volume bar" that shows itself in each tab that is currently playing music?
Re: Mozilla may make Flash click-to-play by default in future Firefox
#67I 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…
To take care of the invisible Flash object problem, Firefox could copy what Chrome does for Java applets and have a bar pop up at the top of the whole page, asking if you want to allow Flash to run on the site in question.
Re: Mozilla may make Flash click-to-play by default in future Firefox
#68Great! I'm just wondering why it took them so long: Opera has had this built-in for ages.
Re: Mozilla may make Flash click-to-play by default in future Firefox
#69I 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…
... 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...
Re: Mozilla may make Flash click-to-play by default in future Firefox
#70Earlier quoted context omitted.
I assume you are suggesting CORS as an alternative. Unfortunately, some APIs (e.g. StackExchange) implement crossdomain.xml but not CORS.
I was thinking of postMessage, I haven't used CORS before but it looks like it ends up giving the same kind of outcome. In my case though I control the server have have the JS on 3rd parties so it is the reverse to what you are saying.
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.