GNOME Bugzilla – Bug 771329
gtk_window_set_skip_taskbar_hint and gtk_window_set_skip_pager_hint not working in Wayland
Last modified: 2018-04-15 00:30:27 UTC
I'm adding a quake mode to my gtk3 terminal emulator where it appears at the top of the screen similar to guake, tilda, etc. As part of this mode I use the APIs gtk_window_set_skip_taskbar_hint and gtk_window_set_skip_pager_hint so the terminal window does not appear as part of the gnome shell overview or has the app in the top bar. Under X11 this works as expected, under Wayland the terminal still appears in the gnome shell overview and has the app menu in the top bar. I'm using the 3.20.9-1 package in Arch Linux.
These are not concepts that Wayland has. I think you'll be much better off doing this sort of thing inside the compositor or with a special compositor interface, under Wayland.
Thanks, I'll have a look at that and see what I can figure out, not very familiar with Wayland at this point. BTW, should those two methods be documented as not functional under Wayland and this changed to a documentation issue?
(In reply to Gerald Nunn from comment #2) > BTW, should those two methods be documented as not functional under Wayland > and this changed to a documentation issue? The API in question sets hints; these are not guaranteed to work depending on platform, window manager, or user configuration. You cannot rely on these hints to have any effect. There's a case that could be made that GNOME Shell could expose an ad hoc protocol under Wayland that GTK+ could use to communicate the same behaviour.
Fair enough, thank you.
(In reply to Emmanuele Bassi (:ebassi) from comment #3) > There's a case that could be made that GNOME Shell could expose an ad hoc > protocol under Wayland that GTK+ could use to communicate the same behaviour. The natural place would be the existing gtk-shell interface.
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla. If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/new