-
Notifications
You must be signed in to change notification settings - Fork 164
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
Internal error dialog is broken if a Dialog component is open #4089
Comments
pekam
added a commit
that referenced
this issue
May 28, 2018
Because vaadin-overlay sets "pointer-events: none" for the body, an opened vaadin-dialog makes the internal error dialog unclickable. Fixes the clicking part of #4089
Seems that the click-bug and the esc-bug are caused by completely different things:
|
pekam
added a commit
that referenced
this issue
May 28, 2018
The message inside the internal error dialog claims that you can continue either by clicking the dialog or pressing the esc-key. However, it seems that continuing with the esc-key was never implemented. Fixes partly #4089
pekam
added a commit
that referenced
this issue
May 29, 2018
Because vaadin-overlay sets "pointer-events: none" for the body, an opened vaadin-dialog makes the internal error dialog unclickable. Fixes the clicking part of #4089
caalador
pushed a commit
that referenced
this issue
May 30, 2018
The message inside the internal error dialog claims that you can continue either by clicking the dialog or pressing the esc-key. However, it seems that continuing with the esc-key was never implemented. Fixes partly #4089 Add tests for the 'internal error' notification Also add '@after' method to reset the SystemMessages changes made by the session expired test.
pekam
added a commit
to vaadin/vaadin-dialog-flow
that referenced
this issue
Jun 4, 2018
Adds tests for this issue which was fixed in Flow: vaadin/flow#4089
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
The text was updated successfully, but these errors were encountered: