-
Notifications
You must be signed in to change notification settings - Fork 83
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
Add public event to notify when the overlay is closed #7422
Comments
The event seems to be public to me. For example the code here compiles. https://github.com/TatuLund/hilla-demo/blob/hilla2/frontend/views/list/contact-form.ts#L196 Also needed types seems to be exported. But the event listener is not getting fired. |
The event is fired by
The fact that VSCode Lit plugin doesn't produce warnings related to this event doesn't mean it is correctly used. Also, this is not a bug but an enhancement ticket. |
In addition to that, there is no run-time JavaScript exception either ... So that further increases the confusion. |
I agree it's a bad DX. But it appears to be an issue of the Lit analyzer tools (including VS Code Lit plugin) that are lacking proper events support. I reported a few issues related to this e.g. runem/lit-analyzer#143 and runem/lit-analyzer#155 You can actually verify that by using e.g. At the same time, I don't think adding an event listener to a non-existing event is supposed to produce an extension. |
Ok, got it. So there is a workaround
|
Describe your motivation
Currently,
vaadin-dialog
andvaadin-notification
don't notify about closing completed.The
opened-changed
event isn't suitable since it is fired before the closing animation.Describe the solution you'd like
vaadin-overlay-closed
event added in feat: dispatch an event after overlay closing completed #5397 publicly invaadin-dialog
(and possibly alsovaadin-confirm-dialog
for consistency)vaadin-notification
that should be fired in_removeNotificationCard()
method.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: