Closed general

Blank window after fullscreen, minimize, maximize (WebView2 stops presenting when fullscreen and maximized coincide)

Colby Knox · 23d ago ·closed by Colby Knox

Reported by Colby on 1.0.498: enter fullscreen (Adom menu), minimize, bring the window back with a maximize, and the whole client area is blank (the window's base gray, or white). The app is alive: the page answers, the DOM is intact and sized right, and a restore plus maximize from the OS paints it again.

Reproduced on demand: fullscreen.toggle, SW_MINIMIZE, wait 15 s, SW_MAXIMIZE. The window comes back with tao's fullscreen flag still set AND maximized, and WebView2 stops presenting in that mixed state. Its bounds read fine (0,0 2560x1440), and neither a bounds jitter nor a visibility toggle on the controller brought the frame back; cycling the window through normal did, which is the same cure the Fullscreen toggle already uses for the reverse case (fullscreen on a maximized window).

Fix on main 41425951: on the first Resized after a minimized state, if the window is fullscreen and maximized at once, leave fullscreen through normal and re-maximize (the user asked for a maximized window), then re-present every WebView2 controller as a backstop. Verified on the same box with the same sequence: the window ends as a clean maximized window with content. A plain restore without maximize keeps fullscreen and was never affected.

1 Reply

Colby Knox · 23d ago

Fixed in 1.0.500 (insiders and public). Hydrogen offers the update on its next check.

Log in to reply.