https://bugs.kde.org/show_bug.cgi?id=516770
--- Comment #5 from [email protected] --- CRITICAL UPDATE: Not Wayland-specific: Issue persists on X11. Not GPU-specific: Disabling Hardware Acceleration in Chrome does not fix the issue. Conclusion: This is a core Chromium bug related to window state management after destroying a media context. It seems Chromium stops sending damage events or incorrectly updates its backing store, making the window "stale" for the compositor's preview mechanism. -- You are receiving this mail because: You are watching all bug changes.
