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
Mark dependent abort signals as aborted before firing events
The assert in 4.2.1 of "create a dependent abort signal" fails when
creating a dependent signal while dispatching abort events or running
abort algorithms if abort had not yet been propagated to one of the
sources.
This fix splits "signal abort" into two phases: first, set the abort
reason on the signal being aborted and all of its unaborted dependents;
next, run the abort algorithms and dispatch events for the signal and
those same dependents. Note that:
1. Dependent signals do not themselves have dependent signals, which
means it's unnecessary to recursively call "signal abort"
2. This approach retains the existing event dispatch order, while
ensuring the abort state is synced before any JS runs
This fixeswhatwg#1293.
0 commit comments