Repository navigation
Fix "Stacking order can only be calculated for elements with a common ancestor" error - #771
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
The document
pointermovehandler callsisViableHitTarget, which compares the stacking order ofevent.targetand the panel group. If the target is removed from the DOM while the event is being dispatched, the two elements no longer share an ancestor, and the vendoredcompare()throws:The fix is for
isViableHitTargetto returntrueearly if either the pointer target or the group element is no longer connected (!isConnected). An element that's been removed isn't rendered, so it can't be covering the separator.Resolves #769