You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue: Mouse up events that end up outside of the modal area, trigger the background click to close the modal.
This can be reproduced with some highlightable text, such as in an input. For example:
If a user highlights the text in a text input and then moves the cursor outside of the modal area while still highlighting, the mouse-up event will close the modal, interrupting what the user was working on.
Background exit should be triggered by mouse down on the background area not the modal frame, and then close when mouse up.
Solution: onmousedown, should start listening to onmouseup
The text was updated successfully, but these errors were encountered:
gian7sm
added a commit
to gian7sm/Modal
that referenced
this issue
Jun 23, 2023
Mouse click, down, and up events will be handled to avoid closing the modal by accident.
This avoids accidents when highlighting text and dragging the mouse cursor outside of the modal area (into the background).
Solves Blazored#518
This also allows the user to escape closing the modal by dragging the mouse click back into the modal content area.
Mouse click, down, and up events will be handled to avoid closing the modal by accident.
This avoids accidents when highlighting text and dragging the mouse cursor outside of the modal area (into the background).
Solves #518
This also allows the user to escape closing the modal by dragging the mouse click back into the modal content area.
Co-authored-by: Chris Sainty <chrissainty@users.noreply.github.com>
Issue: Mouse up events that end up outside of the modal area, trigger the background click to close the modal.
This can be reproduced with some highlightable text, such as in an input.
For example:
If a user highlights the text in a text input and then moves the cursor outside of the modal area while still highlighting, the mouse-up event will close the modal, interrupting what the user was working on.
Background exit should be triggered by mouse down on the background area not the modal frame, and then close when mouse up.
Solution: onmousedown, should start listening to onmouseup
The text was updated successfully, but these errors were encountered: