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
Windows marked mir_window_state_fullscreen
appear behind shell components
#3274
Comments
Actually, I believe the And a fullscreen/maximized window can't be "always on top", so that seems to hold with the above. |
Also note that shell components using layer-shell choose which layer to be in: <entry name="background" value="0"/>
<entry name="bottom" value="1"/>
<entry name="top" value="2"/>
<entry name="overlay" value="3"/> That might also need to be considered. |
Would this be weird for transparent windows to suddenly not see the full attached view behind them? They would only see the other windows that are there, and none of the shell components |
Transparent fullscreen windows? Not on a layer? Sounds wrong :) |
I'm thinking maybe I want to fullscreen my terminal or something 🤔 |
The easiest thing here IMO is:
|
Isn't putting the panels into "bottom" the easiest thing to do? |
Wouldn't the idea of "fullscreen" in regards to certain panels in this case? e.g. I play a game that wants the full screen, but |
I think this is partially artifact of the lack of semantics in layer-shell, combined with some missing semantics in xdg-shell.
Some of this seems to be that we're not quite doing what existing protocols expect. For example,
so we could just stack them there, and they'll stack over the panels (which alt-tab won't focus). |
I agree with Chris. It would be appropriate for fullscreened windows to appear on the top layer so that they are above all panels, but below any overlays (e.g. the lockscreen). However, you still may want to show a non-fullscreened app above a fullscreened app (e.g. I |
Repro
waybar
mir_window_state_fullscreen
waybar
when it should be covering itThe text was updated successfully, but these errors were encountered: