Adobe Flash’s death has been slow and painful, and today Google seems to deal it another blow. Planning to start blocking most Flash content with Chrome, with the change focused and targeted toward the end of this year.
Google has outlined a plan to push HTML5 by default in Chrome, instead of Flash. In Q4 of 2016, the search giant will only serve Flash by default for the top 10 domains that still depends on the plugin and extension. Chrome will display the HTML5 experience if it’s available, but if Flash is required, the user will be asked whether Flash can be allowed to run on it or not.
From years, Flash was been and is on its way. Not only is the tool a security nightmare, with new vulnerabilities popping up regularly, but the market has been slowly rather surely moving away from plugins in favor of HTML5. Chrome and Flash, in particular, have had complicated relationship, though.
This change still doesn’t fully remove Flash from Chrome, while it is included in Google’s browser by default, which it has been slowly but surely De-empasized. To avoid annoying people with too many prompts, such of those includes YouTube, Facebook, Yahoo, Twitch, and Amazon, Flash been used on these ten domains. But they’ll have a one year exemption. After that, it sounds like they’ll have Flash blocked by default, just like everyone else.
It’s still in there, Flash and be able to be widely run, so long as people keep giving it permission. Disabling it by default still offers protections against unwanted and potentially malicious content. By far it encourages web developers to make the jump to HTML5, so that people aren’t discouraged from leaving their site.
Since Google began enabling Flash blocking on a very limited scale a year ago, when it started “intelligently” pausing unnecessary content as a way to preserve battery life. That’s the stock setting right now; this plan pushing things much further.
In September 2015, Google Chrome 45 started automatically pausing less-important Flash content (ads, animations, and anything that isn’t “central to the webpage”). Now, Google really wants to focus hardly on the central content, such as games and videos. If you’re interested in, you can simply enable the settings that Google is planning to switch over to.
Hidden inside of Chrome’s preferences page (under privacy and then content settings), where you may find an option called “let me choose when to run plugin content” It will block all Flash content until you right click on it and choose to have it enabled. There will be a setting to “Allow Sites to ask to run Flash” (Ask the first time only), “Allow Sites…” (right-click to play), and “Never run Flash content” (disable the plugin entirely). Users will be able to manage their individual site preferences.
Here is Google’s “HTML5 by Default” proposal for Chrome:
- If a site offers an HTML5 experience, this change will make that the default experience.
- When a user encounters a site that needs Flash Player, a prompt will appear at the top of the page, giving the user the option of allowing it for a site.
- If the user accepts, Chrome will advertise the presence of Flash Player, and refresh the page.
- Chrome will honor the user’s setting for that domain on subsequent visits.
- To avoid over-prompting users, we will initially ship with a whitelist of the then top 10 sites (based on aggregate usage). This whitelist will expire after one year.
Point to be noted! Flash is a menace on battery life and is continually found to have serious security flaws, so its eventual disappearance will be celebrated at every step. What do you think?