This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21645 - [HTML] editorial: 9.2.6.3: "perform the next step asynchronously"
Summary: [HTML] editorial: 9.2.6.3: "perform the next step asynchronously"
Status: CLOSED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-09 22:51 UTC by Michael Dyck
Modified: 2013-04-11 01:40 UTC (History)
2 users (show)

See Also:


Attachments

Description Michael Dyck 2013-04-09 22:51:58 UTC
In 9.2.6.3 "Shared workers and the SharedWorker interface",
step 8.7.5 says:
    Return worker and perform the next step asynchronously.

but there's more than one step left, so it's unclear what to do after 8.7.6.

Change "step" to "steps"? (Or better, "next step" to "remaining steps"?)
Comment 1 Ian 'Hixie' Hickson 2013-04-10 22:43:22 UTC
Wow, this dates way back to before we had a way to queue tasks. Apparently when I added the text to queue the task, I just forgot about the previous step. And then, later, added more steps.

Anyway, I moved the 'return' down to the abort step and removed the stuff about asynchronously doing anything, since as far as I can tell you can't detect if the remaining steps are done synchronously or not (or if you can detect them, it's a race condition, and so you'd want them done synchronously).