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 21707 - [HTML] editorial: 10.2.2: "in the background"
Summary: [HTML] editorial: 10.2.2: "in the background"
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-16 03:54 UTC by Michael Dyck
Modified: 2013-04-20 00:46 UTC (History)
2 users (show)

See Also:


Attachments

Description Michael Dyck 2013-04-16 03:54:49 UTC
In 10.2.2 "The EventSource interface",
in the algorithm for the EventSource() constructor,
step 6 says:
    Return the new EventSource object,
    and continue these steps in the background (without blocking scripts).

Similarly, in 10.3.2 "The WebSocket interface",
in the algorithm for the WebSocket() constructor,
step 7 says:
    Return a new WebSocket object,
    and continue these steps in the background (without blocking scripts).

In each case, does the second clause mean the same thing as running the
remaining steps asynchronously (the phrasing used elsewhere in the spec)?
Comment 1 Michael Dyck 2013-04-20 00:46:04 UTC
[changed to "but continue these steps asynchronously"]