Below is a list of specs known to Webref that reference the in parallel term.
Unchecked specs contain at least one algorithm with steps that resolve/reject a promise while running in parallel without queuing a task first, or have some related issue described in a short comment next to the spec name. In other words, they define something like:
X. Run the following steps in parallel:
Resolve/Reject p with foo.
... instead of:
X. Run the following steps in parallel:
Queue a task on [task source] to resolve/reject p with foo.
Checked specs look correct at first glance. Some of them simply reference the term in a note and do not define actual algorithms with steps in parallel.
[ ] Fetch Standard - steps under 16 of HTTP-network-or-cache fetch algorithm look suspicious as close stream ends up rejecting a promise without queuing a task
The full list was computed automatically from Webref data. The review process was manual. I may have missed problems in some of the specs.
Some specs use "in parallel" but do not link back to its definition in HTML. I added some of them manually above. No doubt there are other specs in that category!
Below is a list of specs known to Webref that reference the in parallel term.
Unchecked specs contain at least one algorithm with steps that resolve/reject a promise while running in parallel without queuing a task first, or have some related issue described in a short comment next to the spec name. In other words, they define something like:
... instead of:
Checked specs look correct at first glance. Some of them simply reference the term in a note and do not define actual algorithms with steps in parallel.
Other specs that use "in parallel" without linking to its definition in HTML:
Notes: