Commit afb3d14
fix: prevent Chromium corner glitch on restore after app-initiated minimize
Chromium-based browsers use xdg_toplevel.set_minimized for their own
title bar minimize, which causes Wayland surface staleness. On restore,
the stale surface makes the GLSL rounded corner shader render with wrong
bounds, producing a visible glitch until focus fires and self-corrects.
Fix by scheduling a refreshRoundedCorners call 250ms after unminimize
for Chromium windows, giving the Wayland surface time to deliver a fresh
frame before the shader bounds are recomputed.
Compositor-initiated minimizes (Super+H/D) do not cause surface staleness
and are unaffected. The overview thumbnail continues to show the stale
Chromium surface while minimized — this is a known Chromium/Wayland
limitation outside the extension's control.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>1 parent 5a9563d commit afb3d14
1 file changed
Lines changed: 18 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
24 | 24 | | |
25 | 25 | | |
26 | 26 | | |
| 27 | + | |
27 | 28 | | |
28 | 29 | | |
29 | 30 | | |
| |||
171 | 172 | | |
172 | 173 | | |
173 | 174 | | |
| 175 | + | |
| 176 | + | |
| 177 | + | |
| 178 | + | |
| 179 | + | |
| 180 | + | |
| 181 | + | |
| 182 | + | |
| 183 | + | |
| 184 | + | |
| 185 | + | |
| 186 | + | |
| 187 | + | |
| 188 | + | |
| 189 | + | |
| 190 | + | |
| 191 | + | |
174 | 192 | | |
175 | 193 | | |
176 | 194 | | |
| |||
0 commit comments