Google has come up with a plan to use HTML5 an alternative to Flash by default in Chrome. The company plans to only serve Flash by default for the top 10 domains that still depend on the plug-in, in Q4 2016. Chrome will display the HTML5 experience if it’s available, the user will be asked whether Flash can be allowed to run or not, only when required.
The market has been slowly moving away from plugins in favor of HTML5. Google’s browser has included Flash by default, but now it has been slowly and surely less-emphasized.
Here is Google’s “HTML5 by Default” proposal for Chrome:
Now Flash player will come as a package with Chrome, however, its existence will not be displayed by default, namely in Navigator.Plugins () and Navigator.MimeTypes ().
- If a site suggests an HTML5 experience, this modification will make that default experience.
- A prompt will be appearing on the top of the page, when a user encounters a site that needs Flash Player, giving the user the option of the following for a site.
- If the user accepts, Chrome will display the existence of Flash Player, and refresh the page.
- The user’s setting for that domain on subsequent visits will be honored by the Chrome.
- To avoid over-prompting users, initially, they will transfer with the whitelist of the then top 10 sites (based on average usage). This whitelist will expire after one year.
The main goal of these browser makers is pushing as many sites as possible to HTML5, which increases the performance and in terms of web standards. There will be security gain as with this advancement. Google has previously said it plans to have Google's Chrome serve HTML5 by default in Q4 2016. Now the timeframe has been narrowed to December.