Tech reporters, please fact-check your articles.

Various sites last night began reporting that Chrome 55 blocks Flash, except for a "top 10 list" of sites.

Except that it doesn't, and the details are in various posts on this public discussion thread: https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/ad7Posd6cdI

Basically, starting sometime this month, 1% of Chrome 55 users (rather than all users) will be assigned to an experiment which uses HTML5 by default over Flash when possible. On some sites this isn't possible and will trigger prompts to re-enable Flash instead. These prompts will only occur on sites whose Site Engagement score is lower than 1 (meaning the user has never visited the site before).

If all goes well, Chrome 56 will increase this rollout to all users, and then throughout 2017 the minimum Site Engagement score will be increased, gradually widening the scope of prompting, so that sites the user uses the most will be affected last. (This gives sites time and motivation to change to something other than Flash while minimizing the negative impact of this on their users.) The browser will also remember the response to the prompt so users aren't forced to say "yes" every time.

I know "Chrome kills Flash" is a more exciting headline than the above, but it's also a misleading one. And explicitly reporting details discarded months ago, like the "top 10 list" idea, is just lazy.

(PS: More about the "blocking" here is at https://docs.google.com/presentation/d/106_KLNJfwb9L-1hVVa4i29aw1YXUy9qFX-Ye4kvJj-4/edit#slide=id.p .)
Shared publiclyView activity