Fixed hover events in Shadow DOM #6021
Merged
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
archmoj
added
status: reviewable
bug
archmoj
reviewed
Nov 12, 2021
|
💃 |
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 #5277
Reverts #5256
The 'target' property changes when bubbling out of Shadow DOM. Unfortunately, that conflicts with event throttling, as the 'target' changes before the throttler's setTimeout calls the hover callback. I added code that captures the original target and passes it to the hover callback.
I'm reverting a previous commit because composedPath isn't needed when the event target is read before the event bubbles outside the shadow root.