Google is Phasing Out Support for Adobe Flash in the Chrome Browser

toggle-button
flash-ending-300px.jpg
 
This is good news. At long last Google is phasing out support for Flash from its highly popular Google Chrome Browser. By the end of the year Flash will be replaced as the default media plugin in Chrome by HTML 5.  Although it will no longer be the default media plugin it will for the time being, be still included with the browser but its use will be limited by default to 10 Flash intensive sites: YouTube.com, Facebook.com, Yahoo.com, VK.com, Live.com, Yandex.ru, OK.ru, Twitch.tv, Amazon.com and Mail.ru. Other sites can be enabled for Flash by manual over-ride.
 
For years it has been known that Adobe Flash is prone to security vulnerabilities but it historically has been so widely used by websites for videos and animated site features that it has been largely impractical to do without it.  This started changing when Apple dropped support for Flash in iOS and has accelerated since the the release of HTML 5 which offered a viable and more secure alternative.  
 
Many websites have now dropped Flash altogether and with the Google announcement its days are numbered. This is welcome news from a security perspective.
 
More details can be found in Google’s HTML by Default proposal
 

Please rate this article: 

Your rating: None
3.5
Average: 3.5 (14 votes)
toggle-button

Comments

The problem with changing video players lies not with the users but with the sites. When the security warnings first appeared I disabled my Flash player, only to find that the news and blog sites I was redirected to no longer worked.
How long ago was that? It feels like years.
I suspect there are few users who care which player they use. If the content providers drop Flash, it’s gone.

What I really hope is that they don't make it so that it's impossible to use flash with Chrome. Mind you, I pretty much stopped using Chrome when they stopped supporting extensions that weren't from the Chrome web store, I stick with Firefox now, and I hope they don't start doing the same thing. If I want to run a certain piece of software, I shouldn't be told not to by some "authority" in Mountain View that I can't.

Side note: I honestly think it didn't really start with Apple not allowing flash to run on iOS (called iPhone OS back then), it started when Adobe released flash for Android and it was not very efficient at all, which made flash very unattractive for mobile platforms (interestingly enough Blackberry, back then RIM, showed us that it actually was possible to make flash work well on mobile with its implementation on the playbook). That was really the first hit, because Apple would have implemented flash if it were popular on mobile. Adobe is solely responsible for the catastrophe that flash turned into.

I hope Firefox follows suit. My experiences for a long time are that Adobe Flash causes more browser crashes than other factors.

New subject: Is Youtube really all that flash intensive? I rarely see flash activated when I watch a Youtube video.

I don't really care for Flash bashers. The reality is that any format that has a lifespan as long as Flash did will inevitably develop security issues. In time we will see security issues crop up with the HTML format and then developers will once again go back to the drawing boards.

@crosseyedlemon:

I don't believe that the lifespan alone is the primary reason.

The long lifespan rather points to an old software design and old internal structures. That's a very similar scenario as MS was facing with IE which is now (Win 10) officially deprecated.

As stated in another comment, it's mostly the content providers. If they would switch all their content to HTML5 there would be no need for discussions like these here. Google proves this point with their "exceptions list".