[whatwg] Websockets Client API

[Robert O'Callahan]

On Mon, Feb 21, 2011 at 11:38 AM, Toni Ruottu <toni.ruottu at iki.fi> wrote:

> I believed that the browser is expected to somehow magically delay the
> events until a callback has been registered. At least that is how it
> seems to work at the moment. The specification could be clearer about
> this.
>

It's not magic, the spec is perfectly clear. The language about "queuing a
task" ensures that any callback events fire after the current task (e.g. the
script event handler that created the Websocket connection) has run to
completion.

Rob
-- 
"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]