-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Dynamic Dialog Ref crashes the App on close #11230
Comments
Hi, I can't access the code of the example, could you please provide an editable Stackblitz link? Regards |
Hi @cetincakiroglu, can you check this one: https://stackblitz.com/edit/github-xqz8yh?file=src/app/app.component.ts |
Hi, So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you reopen the issue so we can include it in our roadmap? Best Regards, |
Hi @mertsincan , I have checked and apparently, the issue still persists. |
Hello, I also encountered the same problem in Angular version 12 When this.ref.close() command was executed in the dialog, the page was refresh automatically And my problem was solved in such a way that inside the buttons that executed this command I gave them the type "button" and my problem was solved |
I'm submitting a ...
Plunkr Case (Bug Reports)
Demo: https://github-xqz8yh.stackblitz.io
Current behavior
If you want to show a dialog until some action is done, the app will crash on dialog close.
Expected behavior
It should open a dialog for x amount of time and then close it without crashing the application.
Minimal reproduction of the problem with instructions
Please tell us about your environment:
OS: Windows 10
IDE: Visual Studio Code
Package manager: npm
Angular version: 13.X
Language: [all]
Node (for AoT issues):
node --version
= 14.17.5The text was updated successfully, but these errors were encountered: