Adobe plugin snubbed for HTML5
Google Chrome 55 will effectively make all Flash content click-to-play by default, marking a fresh push by the web giant for a HTML5-only world.
When visiting a website with Chrome 55, due out in December, the browser will prefer to use HTML5 for video, animations and other content.
If there is no HTML5 available and instead just Flash, you’ll be asked to explicitly enable the Adobe plugin to view it.
This will pile immense pressure on web developers to use HTML5 and ditch Flash because Chrome will deliberately stall the plugin’s user experience.
It’s effectively throwing Flash out into the cold winter’s night.
There is no more room at the inn.
Google says it prefers HTML5 because it’s faster to load than Flash and easier on handhelds’ batteries.
But the elephant in the room is Flash’s dreadful security record: it is a screen door that lets the sewage of the internet seep in and infect computers.
Googler Anthony LaForge, who oversees Flash support in Chrome, blogged today:
Adobe Flash Player played a pivotal role in the adoption of video, gaming and animation on the Web.
Today, sites typically use technologies like HTML5, giving you improved security, reduced power consumption and faster page load times.
Going forward, Chrome will de-emphasize Flash in favor of HTML5.
In December, Chrome 55 will make HTML5 the default experience, except for sites which only support Flash.
For those, you’ll be prompted to enable Flash when you first visit the site.
Aside from that, the only change you’ll notice is a safer and more power-efficient browsing experience.
This comes after Chrome 42 made ads and other cruft click-to-play by default, and Google vowed to kill off Flash auto-play for good in its software by the end of the year. ®
Sponsored: Global DDoS threat landscape report