You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Flush during flush leads to not all tasks being executed #35
Browser:
all | Chrome XX | Firefox XX | Edge XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView
Language:
all | TypeScript X.X | ESNext
Current behavior:
If one of the queued micro tasks calls flushMicroTaskQueue
Queue enters the second flush cycle even though flushing is set to true
after which length of queue is set to zero
but for 1st flush call index is greater then length of queue at this point
and leads to unexpected behavior
Expected/desired behavior:
What is the expected behavior?
If queue is already flushing we should ignore the second call
What is the motivation / use case for changing the behavior?
prevent uncertainty
Activity
Alexander-Taran commentedon Aug 10, 2021
@bigopon ping
bigopon commentedon Aug 19, 2021
@Alexander-Taran thanks for the ping. Will proceed with the merge and a new npm version soon.
Alexander-Taran commentedon May 24, 2022
@bigopon ping (-: