fix: maps mouse events to document for improved UX #93
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.
Problem
The mousemove and mouseup events were previously bound directly to the board element div. This caused difficulties for users trying to select colors at the extreme edges of the color picker, such as full black or full white. Users had to position their mouse precisely at the edges, which was often impossible, resulting in inaccurate color selection (e.g., a greyish color instead of full black or white).
Solution
The mousemove and mouseup events have been remapped to the document object. This change ensures that the color selection can be accurately tracked even when the mouse moves outside the boundaries of the color picker element. Users can now easily select colors at the extreme edges without needing to precisely position their mouse.
Video
✅ Improved UX (note how my cursor is leaving the board element while holding the left mouse button and still picking the proper color):
CleanShot.2024-07-24.at.16.44.31.mp4
❌ Previous state:
CleanShot.2024-07-24.at.16.44.02.mp4