-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shouldn't close on Esc #62
Comments
I’m trying to guess here, but I assume you are perhaps misusing a confirm dialog for some other purpose? 😃 A standard confirm dialog should always be closable with the Esc key, so this issue could be considered “invalid”. But since it should be straightforward to let you do this (just bind the property), it should be alright to fix. |
I won't say if your guess is correct or not 😈 But let's consider a proper confirm dialog, which is |
Hmm, true, I skipped that for some reason completely. It seems we’ve skipped that use case completely in our initial design. Thanks for pointing it out 👍 Would you have a good example of this kind of dialog? |
The user initiates a transactional processing on the server, which encounters some kind of issue producing the result and needs a user confirmation to be able to proceed or not: the user is prompted with a confirm dialog which asks if the action should be committed or rolled-back, no other choices permitted. |
To wrap it up (in my opinion, obviously):
This way we can have a dialog which permits to cancel by pressing ESC, but also can force the user to explicitly press the "Cancel" button to close the dialog wihtout any choice; plus, the dialog can force the user to "Accept" or "Reject", as described by the discussed scenarios. |
Despite having set
no-close-on-esc
in the wrappedvaadin-dialog
, pressing Esc closes the dialog.The text was updated successfully, but these errors were encountered: