Top Bar staying when you click back on

[Yess-Papa]

So when in Fullscreen and you click to another monitor this grey bar comes at the top. When clicking back into the tool it doesn't disappear and you have to go out of full screen and back into full screen to get rid of it.

(I've explained this really badly but I have a screenshot below)

[apoint123]

Okay, thanks for the report and the screenshot!

Actually, I suspect this might be a bug with Windows itself rather than the tool. I’ve noticed this exact same behavior in other software recently, likely caused by some recent Windows updates. It seems like the OS is struggling to render the borderless fullscreen state correctly when the focus shifts to another monitor.

I'll keep an eye on it, but it seems to be an upstream issue for now.

[iPixelGalaxy]

Okay, thanks for the report and the screenshot!

Actually, I suspect this might be a bug with Windows itself rather than the tool. I’ve noticed this exact same behavior in other software recently, likely caused by some recent Windows updates. It seems like the OS is struggling to render the borderless fullscreen state correctly when the focus shifts to another monitor.

I'll keep an eye on it, but it seems to be an upstream issue for now.

That’s quite goofy actually, in my case I’m using Windows Server and it seems to affect it as well

Is it possible that’s it’s a GPU driver issue? I recently updated my AMD GPU Drivers and that’s when it seemed to start happening, but doesn’t seem limited to AMD 🤔

[apoint123]

That’s quite goofy actually, in my case I’m using Windows Server and it seems to affect it as well

Is it possible that’s it’s a GPU driver issue? I recently updated my AMD GPU Drivers and that’s when it seemed to start happening,
but doesn’t seem limited to AMD 🤔

Yeah, that is interesting regarding Windows Server.

While the GPU driver timing is suspicious, I'm actually starting to suspect this is caused by a recent update to the WebView2 Runtime (which Tauri relies on).

WebView2 updates independently from Windows Update (and the OS version), which would explain why it's affecting Windows Server and standard users alike. I've even noticed users who have Windows Updates completely disabled are still encountering this, so it points to a regression in the latest WebView2 release regarding how it handles title rendering.

[iPixelGalaxy]

That makes alot more sense
Any ideas on how to downgrade that WebView2 component?

[apoint123]

Yeah, unfortunately, downgrading WebView2 is really difficult for end-users.

It's designed to be always auto-updating, and Microsoft doesn't provide an easy way to roll it back without potentially breaking other apps that rely on it. It’s deeply integrated into the OS now.

We basically have to wait for them to push a fix in a future update, or you can try searching for solution on Google.

[Yess-Papa]

Seems to be fixed now. Guess WebView pushed an update

[iPixelGalaxy]

Seems to be fixed now. Guess WebView pushed an update

and I had just figured out a hacky way to put 143 back on lol