Google bug made zooming into images a nightmare, but there’s a fix

The issue originated from a change in Chrome’s image‑decoding pipeline introduced in version 124.0.6367.91, which inadvertently triggered a GPU‑driven blackout whenever a page attempted to scale rasterized bitmaps beyond their native resolution. Android Authority documented that the fault was not confined to Chrome; any app leveraging the Android System WebView component—such as Samsung Internet, Microsoft Edge, and several native Android apps—exhibited the same flickering and loss of visual data when pinch‑zooming or programmatically enlarging pictures. Developers reported that the blackout persisted across devices running Android 12 and 13, and that the symptom appeared regardless of image format (JPEG, PNG, WebP). Google’s response included a temporary flag—chrome://flags/#disable-image-zoom-blackout—that forces the renderer back to the legacy path, and a definitive fix slated for Chrome 124.0.6367.95, which restores the original texture handling logic.

The glitch surfaces at a time when browsers are vying to offer richer, media‑heavy experiences on mobile. Chrome’s market share on Android hovers above 70 %, and its WebView underpins a large swath of third‑party apps; a regression that degrades image fidelity directly impacts e‑commerce platforms, news sites, and social feeds that rely on smooth zoom interactions. Competitors such as Samsung Internet and Brave have already rolled out patches that bypass the faulty code path, underscoring how quickly the ecosystem can fragment when a core component misbehaves. The episode also highlights the tension between aggressive performance optimizations—like GPU‑accelerated decoding—and the need for rigorous regression testing across the myriad Android configurations that developers must support.

Looking ahead, developers should monitor the Chrome release notes for the confirmed fix and consider shipping a fallback that disables hardware‑accelerated zoom on affected devices until the update propagates. Enterprises with critical image‑intensive workflows may need to test their WebView‑based apps against the flagged workaround to avoid user churn. The incident serves as a reminder that even mature platforms can introduce regressions that ripple through the Android app ecosystem, making proactive testing and rapid response mechanisms essential for maintaining a seamless user experience.