-
Notifications
You must be signed in to change notification settings - Fork 450
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gtk: make sure that window-decoration is honored on all paths #4130
gtk: make sure that window-decoration is honored on all paths #4130
Conversation
I confirm that this fixes the regression. |
With this config the problem of the absent window decoration still reproduces:
The GTK titlebar is not shown: correct Pressing ctrl-z shows some minor change to the window border, but also then the WM decoration with its titlebar is not displayed. |
I don't think that this is directly a result of this PR. I'm getting the following logs when I try and toggle window decorations:
|
Indeed this PR is not the cause, but it is related. The problem is originally from commit a7c93cd I think, as there are multiple commits modifying Window.zig it's not easy to determine, but if this PR is to "make sure that window-decoration is honored on all paths" the mentioned issue also needs to be solved. |
Ah, I think I understand. When The decorations are toggling but it's very hard to see as it's basically just a shadow. |
I'm not sure how to address this, but without a fix for the regression ghostty is no longer usable in case gtk-titlebar=false. |
Hmm... The user has explicitly told Ghostty that they do not want a titlebar via |
Indeed gtk-titlebar is false, but window-decoration is true so the native window title bar should be shown just like it was before today's commits. This is from the documentation
There is no word of gtk-titlebar=false overruling window-decoration=true |
I checked out 1.0.0 and tested:
Titlebar was shown on launch but could be hidden with
Worked as expected.
Worked as expected.
So I don't think that this was ever working 100% as one would expect. |
@artist-artix Please open a new discussion about the interaction of |
I have opened #4172
This is exactly as expected and how it is supposed to work when reading the documentation. So in 1.0 this was NOT broken. |
That is not how I would expect things to work, and yes I've read the documentation. So as I said there's both documentation problems and code problems. Please open a new discussion so that we can figure out what the interactions should be between these options rather than continuing the discussion here. |
Fix a regression from #4110 .