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
Specs known to Webref that run steps in parallel and queue a task to resolve/reject a promise correctly are checked in the list below. Unchecked specs are those that define a tleast one algorithm with steps that resolve/reject a promise while in parallel without queuing a task first.
DOM Standard - step 3.2 in the example (but not step 2.3.2 since it merely adds an algorithm that gets called correctly with "queue a task")
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
Specs known to Webref that run steps in parallel and queue a task to resolve/reject a promise correctly are checked in the list below. Unchecked specs are those that define a tleast one algorithm with steps that resolve/reject a promise while in parallel without queuing a task first.
browsingTopics()
queues a global task in step 11.1 that does not seem needed since step does not run in parallelThe text was updated successfully, but these errors were encountered: