Let the custom titlebar act like the system titlebar?

[timwehrle]

So I've been wondering about if I can get the custom titlebar to act like the system titlebar in terms of resizing. I guess the custom titlebar is always slower when I resize the window because it gets rendered in the webview. Is there a way to achieve the same effect like the system titlebar?

With system titlebar
https://github.com/tauri-apps/tauri/assets/115550741/c68c6fef-8408-4d38-b642-e83d5675be97

With custom titlebar
https://github.com/tauri-apps/tauri/assets/115550741/a2fd076b-4970-48d6-abc2-d85051bbfc3f

[FabianLars]

With html/css based titlebars this can really only be fixed by fixing resizing itself which has multiple gh issues like #6322 for example.

The alternative to this would be a native "custom" titlebar which a) is pretty difficult in general and b) basically incompatible with tauri or webview2 depending on the approach (there should be a few discussions on this and wry's github and our discord).

[timwehrle]

And what is the preferred way to solve this problem? Make users use the native bar or just use all the workarounds until something is finally fixed?

[FabianLars]

Depends on your app/needs. If the native titlebar works for you, then i'd recommend sticking to it. If not, try the workarounds or help us fixing the issues :)

[timwehrle]

I mean, I'd like to help, but your response kind of made it seem like it wasn't a Tauri problem, but a webview problem, didn't it? Probably helping with the resizing problem would be good?

[FabianLars]

It's a mix of both/all.

• Chromium's resizing itself is already pretty bad, at least if hardware acceleration is enabled - On that note, if your app isn't too graphics intensive, this may be an option for you? Software rendered resizing should be as smooth as it can get. You can do this by setting --disable-gpu in the additionalBrowserArgs config.
• webview2' resizing somehow seems to be worse than chromium, talking with their team wasn't really fruitful though.
• wry's resizing may also be a tad bit slower than raw webview2, not sure
• Then the issue i linked above comes into play, for some reason resizing is much worse in tauri compared to wry so something in tauri's event loop is pretty messed up. Fixing the actual root causes needs deep tauri knowledge, but integrated workarounds in the spirit of [bug] Resizing on Windows is much slower in Tauri than in Wry #6322 (comment) / refactor: webview as child for WebviewWindow, enhance resizing closes #6322 #8801 may be possible for normal contributors too.

This isn't reallyyy my area of expertise anymore either :/

[timwehrle]

Yea, thanks for the overview. I'll see what I can do or if I can do something lol.