Skip to content
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

ConfirmationService: Cannot show multiple dialogs in quick succession #15916

Closed
davidda opened this issue Jun 28, 2024 · 3 comments
Closed

ConfirmationService: Cannot show multiple dialogs in quick succession #15916

davidda opened this issue Jun 28, 2024 · 3 comments
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@davidda
Copy link

davidda commented Jun 28, 2024

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

  1. Click on button "Does not work". Confirm "Yes" => Second dialog does not show.
  2. Click on button "Works". Confirm "Yes" => Second dialog shows after timeout.

Expected behavior

There should be no time delay needed between two calls of confirmationService.confirm(...)

@davidda davidda added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jun 28, 2024
@quentin-ineat-ca
Copy link

Agree. Same one I opened here : #15725

@raiworld81
Copy link

+1

@mertsincan
Copy link
Member

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 open a new issue so we can include it in our roadmap?

Thanks a lot for your understanding!
Best Regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

4 participants