Drag bug fix #1
Open
Drag bug fix #1
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
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.
We were experiencing a bug when we panned an image with an SVG overlay that made the scroll position jump to the top left position onDragStart. This was caused by the
.getBoundingClientRect()function randomly returning unexpectedly low values which caused the scroll positions to be set to minus numbers.To combat this I have modified the conditional on line 47 to set the
bounds.width/heightusingscrollWidth/Heightif any child nodes are present, rather than multiple child nodes..getBoundingClientRect()is only used when no child nodes are present.