71–80 of 121 posts
I rock click-to-play for plugins in Chrome and it's extremely helpful for browsing speed and enjoyability. No more playing "Which window is that sound coming from?". That said, there are definite usability problems with the current chrome implementation that I hope FF improves on. I'd like a "Load all requested plugins for this page" button. Or a whitelist maybe.
I 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://b…
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.
I 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.
Earlier quoted context omitted.
Firefox canvas really isn't that slow anymore. Every time they increment the major version number, I play a couple of HTML5 games and check out the difference in responsiveness. A highly subjective test, sure, but an effective one. If you take a user-centric view then it's arguably the only test that really counts. You wouldn't believe the difference between FF5 and FF12 playing a game like Canvas Rider[1]. [1]: http…
yeah but consider in the future everyone ditch Flash ads for canvas animation ads, your page will basically have like 1000 embedded blinking and scrolling ads made in canvas.
Earlier quoted context omitted.
Chrome has a click-to-play implementation for Flash? That is not a plugin? Do I have to go to chrome://flags or something?
Yes. 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.
I rock click-to-play for plugins in Chrome and it's extremely helpful for browsing speed and enjoyability. No more playing "Which window is that sound coming from?". That said, there are definite usability problems with the current chrome implementation that I hope FF improves on. I'd like a "Load all requested plugins for this page" button. Or a whitelist maybe.
There's icon in the url bar which you can click to whitelist the current website, and there's whitelist settings as well.
Sometimes this button is necessary if there's a 1x1 flash embed somewhere that is required for the page.
Animated ads are the second most annoying thing on the web after embedded background music.
On a side note: is there an opensource browser who doesn't let a flash video/embed to steal keyboard focus? I tend to use the kb heavily for navigation and this behaviour is frustrating.
Not just flash, all plugins, which is a good security idea, considering how Microsoft likes to slip in theirs via windows update. I see the setting in FF12b5 but not sure if it works yet.
The about:config setting currently works only in Firefox 14, available on the Nightly channel: http://nightly.mozilla.org/