Chrome will block “behind the scenes” Flash content in September, make HTML5 the default for central content in December
Google has shared more details of its plan to replace Flash with HTML5 by default in Chrome. In September 2016, Chrome will block Flash content …
Context & Ripple Effects
Google has been tightening the screws on Flash in Chrome for a year: it started automatically pausing less important Flash content back in September 2015, then announced a click-to-play default for Q4 2016 with an exemption for the ten top Flash-dependent sites. This article fills in the schedule behind that plan — background Flash blocked in September, HTML5 as the default for central page content in December.
The ad side is moving in lockstep: Google already said it will stop running Flash display ads from January 2, 2017, so publishers and advertisers face the same deadline from both the rendering engine and the largest ad network.
First-order effects
- Sites that load invisible Flash modules for analytics, tracking, or background functionality break outright in September unless they ship HTML5 equivalents; only the ten whitelisted top sites keep automatic Flash playback.
- Publishers whose central content still requires Flash get a December deadline before Chrome renders HTML5 instead, with the click-to-play fallback as their last resort.
Second-order effects
- Ad networks and measurement vendors must finish HTML5 conversion of creative and tracking tags ahead of Google's own January 2017 cutoff, since blocked background Flash would silently kill their pixels.
- Rival browsers face pressure to match Chrome's defaults or absorb the compatibility complaints when users blame the browser that still runs Flash rather than the site that still requires it.
Third-order effects
- If the cadence holds — pausing in 2015, click-to-play in 2016, full default blocking by Chrome 76 per the later coverage — plugin technologies die not by deprecation notices but by the dominant browser flipping defaults, making Chrome's release calendar the de facto standard-setting body for the web.
The trend: Browser vendors are retiring legacy web technologies by changing defaults on a published schedule, letting Chrome's roadmap — not standards bodies — dictate when Flash-era content stops working.