Task/htl 113692 limit dragging to header only #1545
Merged
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.
Currently, the entire drawer area is drag-to-snappable. Ideally, this action should only be triggered by dragging the header handle, not other parts of the drawer content.
Previously, this introduced a bug where content scrolling triggered the drag-to-snap behavior, which was then patched with a workaround in #1542 by differentiating touch actions.
However, that approach doesn't work well on real devices, introducing jankiness in the scroll action. Therefore, we're revisiting this with a new approach - using the
useDragControls
hook fromframer-motion
to limit where we can drag (in this case, the header). This way, we're properly compartmentalizing the interactive areas.