Workaround for Zombie DOM Nodes #179
Closed
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
|
actually this is rubbish. its relies on there being more added elements than removed ones, still leaves clickable areas to the side of the list and generally doesnt solve the issue of zombie elements. |
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 adresses #120 (comment)
i've added a story that reproduces the issue based off of @ConneXN good work. my workaround sets the z-index for elements starting their leaving-transition to -1, so they dont catch click events meant for the (visible) element below them.
this is not a solve, seeing as we still have zombie nodes, but it satisfies my current requirments. maybe it helps someone else find a real solution.