-
-
Save skorasaurus/69baa6f6ee7bd5c1a837bee8f12e0814 to your computer and use it in GitHub Desktop.
This file contains hidden or 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
that’s because they’re allowing the native `dialog` element to be used for chrome. the `dialog` element, without extra scripting, does not allow for click/tap outside to close |
This file contains hidden or 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
that’s because they’re allowing the native `dialog` element to be used for chrome. the `dialog` element, without extra scripting, does not allow for click/tap outside to close | |
No. though it’s often an expectation for people to be able to mouse click / touch outside of a modal dialog to close it, it is not a requirement that all modal dialogs be allowed to do so.in some cases, it can be important that someone cannot click/tap outside the dialog to close it. e.g. for a confirmation dialog where an explicit “OK” / confirmation from the user is necessary. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment