Open davidda opened 4 months ago
Calling confirmationService.confirm(...) twice in quick succession will cause the second dialog to not be opened at all or immediately close itself. Only a generous setTimeout of 100ms to 500ms depending on browser speed will fix this.
-
https://stackblitz.com/edit/xcaun3?file=src%2Fapp%2Fconfirm-dialog-basic-demo.ts
17+
17.18.1
Angular CLI App
TypeScript
18.6.1
No response
There should be no time delay needed between two calls of confirmationService.confirm(...)
Agree. Same one I opened here : https://github.com/primefaces/primeng/issues/15725
+1
Describe the bug
Calling confirmationService.confirm(...) twice in quick succession will cause the second dialog to not be opened at all or immediately close itself. Only a generous setTimeout of 100ms to 500ms depending on browser speed will fix this.
Environment
-
Reproducer
https://stackblitz.com/edit/xcaun3?file=src%2Fapp%2Fconfirm-dialog-basic-demo.ts
Angular version
17+
PrimeNG version
17.18.1
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
18.6.1
Browser(s)
No response
Steps to reproduce the behavior
Expected behavior
There should be no time delay needed between two calls of confirmationService.confirm(...)