intellihide: add dropdown menu to handled window types #2014
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Just tested this in GNOME Xorg session, and confirmed that this PR will not change the behavior of dock in Xorg: menus are still above the dock and they are clickable. |
vanvugt
approved these changes
May 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a workaround for issue #2013. As far as I could tell this works in most cases of popup menus (by right clicks) in GNOME wayland session. The only exception I meet is the multilevel popup menu from Telegram (illustrated in #2013), but with showing urgent notifications off it also works without problems.
Meta.WindowType.POPUP_MENUis not added to this list as I find that it has side effects for Qt xwayland programs: on my machine the intellihide is triggered every time I right-clicked in Okular (xwayland). However I could not reproduce this within my GNOME OS VM so it might be caused by other factors.