AbortSignal: Propagate aborted state to dependent signals before firing events
The implementation and spec of dependent signals assumes and asserts that a dependent signal is aborted if any of its sources have been
aborted. But this property does not hold during the abort process, since
intermediate states of abort propagation can be observed. For example,
calling AbortSignal.any([signal]) in an "abort" event listener for one
of signal's sources is a way to observe intermediate state, since the
"abort" event fires before the source signal's dependents are updated.
To fix this, this CL decouples setting the abort state and reacting to
abort event:
- Mark the source signal as aborted
- Propagate the aborted state to any dependent signals
- Run abort steps (run algorithms, fire events) for the source signal
- Run abort steps for each of the dependent signals
PR: whatwg/dom#1295
Change-Id: I65a97eb46b01a0071d661e945f64c90e33954088
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5664649
Commit-Queue: Scott Haseley shaseley@chromium.org
Reviewed-by: Joey Arhar jarhar@chromium.org
Cr-Commit-Position: refs/heads/main@{#1344364}