Component: BlockUI breaks when setting block() before (less than 150ms) unblock() animation finished.

[vincent-cm]

Describe the bug

When setting blocked flag to true too quick (less than 150ms) after previous value false, the block-ui breaks and it won't behave correctly.

Environment

Chrome browser, Stackblitz provided.

Reproducer

https://stackblitz.com/edit/lfiv1x?file=src%2Fapp%2Fblock-ui-basic-demo.ts

Angular version

18.0.1

PrimeNG version

17.18.11

Build / Runtime

Angular CLI App

Language

ALL

Node version (for AoT issues node --version)

20

Browser(s)

No response

Steps to reproduce the behavior

1. Go to https://stackblitz.com/edit/lfiv1x?file=src%2Fapp%2Fblock-ui-basic-demo.ts
2. Fork the project and log in with your account (in order to display logs)
3. Open inspector -> logs (default)
4. Click Simulate HTTP calls button
5. Filter the log BlockUI::Running
6. Observe the blocked UI doesn't work as expected, the log shows the order of block/unblock/destroyModal runs, it seems in incorrect order:
   BlockUI::Running Block block()
   BlockUI::Running Unblock destroyModal()
   BlockUI::Running Unblock unblock()
   BlockUI::Running Block block()
   BlockUI::Running Unblock destroyModal()

Observe the screen is not blocking properly and flickering.

** The code setting up a simulated duration of 10 consecutive HTTP calls,
each is fired upon previous one resolved
It gives two timeout: min delays, and min durations,

1. the block = true only if min delays passed before the HTTP resolves
2. the block = false if it is previously set to true and it lapsed at least min durations,
3. when setting min delays < 150ms, the incorrect behaviour is showing above, leaving an unblock listener running

Expected behavior

If setting the min delay = 200 or above, the blocked area correctly represents the duration of the block and the delay of start blocking.
no flickering over the blocked area.

[github-actions]

Due to PrimeNG team's busy roadmap, this issue is available for anyone to work on. Make sure to reference this issue in your pull request. ✨ Thank you for your contribution! ✨