Here is the proposed plan:
– 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.
Google went on to propose:
“When a user encounters a site that attempts to load a Flash Player, which they have not previously approved, a prompt will appear to run Flash Player on that domain. If user allows Flash Player to run we will store that preference and refresh the page with Flash Player enabled.”
All site owners using Flash Players should be motivated, if not by Flash security concerns, then by the loss of pageviews from visitors to their site using the Chrome Browser. HTML5 has become the new standard and it has the added benefit of working in mobile devices as well.