[Webkit-unassigned] [Bug 32332] WebSocket events should be dispatched synchronously

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=32332





--- Comment #1 from Ian 'Hixie' Hickson <ian at hixie.ch>  2009-12-09 11:27:03 PST ---
(In reply to comment #0)
> As per recent WhatWG discussion, everywhere the spec says "queue a task to
> dispatch an event", it actually means "dispatch the event synchronously".

That's only true if the code that would be queueing the task is itself a task
that was queued. In which case, the task in question is simply the task that
was queued. (In other words, it's not the case if the code that would be
dispatching the event is actually running on another thread.)

That is, where the spec says:

   On another thread, if X, queue a task on the main thread that does Y and Z.

...it is fine to implement this as:

   Queue a task on the main thread that, if X, does Y and Z.

...but it's not fine to implement it as:

   On another thread, if X, do Y and Z.


The spec has changed to make the readyState attribute change at the same time
as the events are dispatched (as part of the same task).

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.