Chrome 76 arrives with Flash blocked by default, a new safeguard to prevent Incognito mode detection, PWA improvements, and more
Google today launched Chrome 76 for Windows, Mac, Linux, Android, and iOS. The release includes Adobe Flash blocked by default, Incognito mode detection disabled …
Context & Ripple Effects
Chrome 76 makes good on what the June beta preview promised: Adobe Flash content is now blocked unless a site is explicitly allowed, and Google has shipped its countermeasure against sites probing whether a visitor is in Incognito mode. The release also lands PWA improvements across Windows, Mac, Linux, Android, and iOS.
Blocking-by-default is becoming Chrome's standard mechanism — two releases earlier, Chrome 66 silenced autoplaying video with sound. The Incognito safeguard is immediately contested: within days, researchers surfaced new detection methods, enough that NYT put its paywall back up for Incognito visitors.
First-order effects
- Sites still running Flash must now get explicit user permission per site, accelerating the shift toward opt-in plugins and pushing developers to finish HTML5 migrations.
- Publishers using Incognito detection for metered paywalls lose their free-read loophole at launch — though the NYT episode shows enforcement flipping both ways as detection methods evolve.
Second-order effects
- A cat-and-mouse dynamic sets up between Google's anti-fingerprinting fixes and site-side detection scripts, forcing publishers to pick between paywall integrity and honoring private browsing.
- Adobe loses its last default distribution channel in the dominant browser, shifting Flash's remaining audience to explicit opt-ins that most users won't grant.
Third-order effects
- If the pattern holds through subsequent releases — as it does when Chrome 83 extends Incognito to block third-party cookies and adds DoH — default browser settings become the primary regulatory surface for web privacy, with publishers and advertisers structuring around whatever each release turns off.
The trend: Chrome is converting privacy and legacy-content restrictions into rolling default-on settings, making each release cadence a negotiation between user anonymity and publisher monetization.