Repository navigation
zone.js drains microtasks too early in synchronous event call #44446
Description
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
No
Description
Please see the reproduction. It seems zone.js assumes EventTarget's event call is always a standalone task, which may not be true.
const invoke = (fn) => {
document.body.addEventListener('click', fn);
document.body.click();
document.body.removeEventListener('click', fn);
};
invoke(() => {
Promise.resolve().then(() => console.log(2));
});
console.log(1);Please provide a link to a minimal reproduction of the bug
Please provide the exception or error you saw
Native Chrome/Safari/Firefox outputs `1 2`, while with zone.js outputs `2 1`.
Please provide the environment you discovered this bug in (run ng version)
No response
Anything else?
I noticed this during debugging #41506 (comment) , maybe related.
Reacted by ksz ksz
Reacted by Toni Villena
Activity
JiaLiPassion commentedon Feb 20, 2022
@xiaody , yes, this is a known issue, and may not be fixed in the near future, it there any real world application has some issues because this behavior?
xiaody commentedon Feb 23, 2022
React's
invokeGuardedCallbackImpluses such pattern, it creates afakeNode, add a listener on it and dispatch an event synchronously. #41506(with old version antd) maybe a real world case as I have commented there.mitigate zonejs issue
fix(zone.js): always run microtasks in Promise.then to avoid drain mi…
12 remaining items
fix(zone.js): allow draining microtasks in `Promise.then` (through flag)
fix(zone.js): allow draining microtasks in `Promise.then` (through flag)
fix(zone.js): allow draining microtasks in `Promise.then` (through flag)
fix(zone.js): allow draining microtasks in `Promise.then` (through flag)
fix(zone.js): allow draining microtasks in `Promise.then` (through flag)
angular-automatic-lock-bot commentedon May 16, 2026
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.