WindowSwitcher: Disable hover for a short time after key events - #2903
Open
leolost2605 wants to merge 1 commit into
Open
WindowSwitcher: Disable hover for a short time after key events#2903leolost2605 wants to merge 1 commit into
leolost2605 wants to merge 1 commit into
Conversation
Member
Author
|
@o-alquimista if you want to give this a try I'd be happy about feedback :) |
leolost2605
force-pushed
the
leolost/disable-hover
branch
from
August 13, 2026 21:25
86e7fb3 to
6e91247
Compare
Member
|
I hate magic numbers too but I've also been annoyed by this issue and can't think of a better way to solve it off the top of my head |
leolost2605
force-pushed
the
leolost/disable-hover
branch
from
August 27, 2026 15:30
6e91247 to
47b68d9
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #2727
Disable hovering icons for selection for a short time when initiating and after every key press. See the linked issue for details on the reason. GNOME Shell uses 500ms but I personally found that a bit too much so I went with 300ms but I'm open to suggestions.
Tbh in general I don't like things like this because it is sometimes noticeable but not noticeable enough that you know what's going on and that makes it feel unpredictable and buggy. But ig in this case the main usage is probably keyboard workflows anyways so optimizing for that a bit more might be worth it but I'll leave that to UX.