fix closeThreshold bug #32
Merged
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
|
@Gumbee is attempting to deploy a commit to the emil Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
This is great, thank you |
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 close threshold was not handled correctly and was causing issues with clicks/taps. When clicking on the sheet at a y-coordinate below the close threshold, the sheet would close. Expected behaviour is that it only closes after dragging, not on clicks and that it should close when the user swipes more than
closeThreshold * visibleDrawerHeightregardless of the click/tap y-coordinate.A video of the bug is attached below (note that we need to drag the sheet up first, because the bug only happens when
--swipe-amountis set on the sheet)CloseBug.mov