HideTracker: Assume hovered when revealing via barrier #2634
Conversation
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
lenemter
approved these changes
Nov 15, 2025
In the case that the user triggered the barrier at a point where the panel will actually reveal this is true anyways. And in the case that the user triggered the barrier at a point where the panel won't reveal because it's not wide enough it will make sure that we recheck and unreveal it when the pointer is invalidated.
lenemter
force-pushed
the
leolost/fix-panel-not-unrevealing
branch
from
8aef0cc to
f7c5c97
Compare
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.
From the commit message:
The cause was that triggering the barrier at a point where the dock won't appear will never cause a recheck because we only recheck if the hovered state changed and it wouldn't in that case.
Fixes #2630