- From: <bugzilla@jessica.w3.org>
- Date: Fri, 21 Jan 2011 00:38:46 +0000
- To: public-webapps@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11827 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |ian@hixie.ch Resolution| |WORKSFORME --- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-01-21 00:38:45 UTC --- As far as I can tell the spec is unambiguous about this. The event is called 'connect', it's of type "MessageEvent", does not bubble, is not cancelable, has no default action, has a data attribute whose value is the empty string and has a ports attribute whose value is an array containing only the newly created port, and is fired asynchronously: http://www.whatwg.org/specs/web-apps/current-work/complete/workers.html#shared-workers-and-the-sharedworker-interface The MessageEvent interface additionally says that "Except where otherwise specified, when the user agent creates and dispatches a message event in the algorithms described in the following sections, the lastEventId attribute must be the empty string, the origin attribute must be the empty string, the source attribute must be null, and the ports attribute must be null": http://www.whatwg.org/specs/web-apps/current-work/complete/comms.html#messageevent It looks like WebKit and Opera both have bugs; they should set 'data' to the empty string. Please reopen this bug if I'm wrong. Thanks! -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Friday, 21 January 2011 00:38:48 UTC