fix: masonry scroll handler should rely on event.currentTarget issue#1414 #1420
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.
#1414
The scroll handler should rely only on the scrolltop of event.currentTarget as any of the descendant elements' scroll event will propagate up to the container element. Relying on event.target seems incorrect.
Added a test case which fails if event.target.scrolltop is used.
Also, updated the function
simulateScroll
in spec file. As passing currentTarget toSimulate
is not supported ( facebook/react#4950 ), changed thesimulateScroll
function to set the scrollTop on the desired element.