Skip to main content

Demo 2

setTimeout 0

A zero millisecond timer still waits for the stack to clear.

fully simulatedcurated scenariodoes not execute real code
Short answer

The key output order is A -> C -> B. `setTimeout(..., 0)` schedules work for a later task.

Real-world bug this helps solve

Console output or cleanup runs in an order that does not match the source code order. Useful when you need to defer UI work until after the current event handler.

Common wrong assumption

Assuming 0 means immediate.

Fix direction

Make ordering explicit instead of relying on when a queued callback might happen to run.

Fixed code pattern
Promise.resolve().then(handleMicrotask);
setTimeout(handleTimer, 0);
// Assert/expect the microtask before the timer.
Visual proof

The console lane proves the visible order: A -> C -> B. The active line and queues show why source order changed.

How to verify in a real app

Add temporary logs around the sync line, promise callback, and timer, then confirm the order without adding arbitrary delays.

Share
Loading visual timeline...

Related cases

Continue with nearby confusion while the mental model is fresh.

Recommended next

Was this clear?

This stays local for now. It helps you track where the product still needs sharper cases.

Send detail