13280 2011-07-17 01:06:34 +0000 Why isn't MessageEvent linked to a definition? It's not at all clear what this object is. And the postMsg API has a MessageEvent, but that object doesn't have the "target" property, which is used in the sample code below. A lot more information about Mess 2011-07-17 14:29:21 +0000 1 1 1 Unclassified WebAppsWG Web Workers (editor: Ian Hickson) unspecified Other other RESOLVED DUPLICATE 12510 http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal --- 1 contributor ian ayg mike public-webapps public-webapps-bugzilla oldest_to_newest 51182 0 contributor 2011-07-17 01:06:34 +0000 Specification: http://dev.w3.org/html5/workers/ Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: Why isn't MessageEvent linked to a definition? It's not at all clear what this object is. And the postMsg API has a MessageEvent, but that object doesn't have the "target" property, which is used in the sample code below. A lot more information about MessageEvent would be very helpful. Posted from: 174.21.138.224 User agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_8; en-us) AppleWebKit/533.21.1 (KHTML, like Gecko) Version/5.0.5 Safari/533.21.1 51184 1 ayg 2011-07-17 14:29:21 +0000 This is another spec-splitter bug. The links do work in the WHATWG version: http://www.whatwg.org/specs/web-apps/current-work/complete/workers.html#workers But the script that splits it up to make the various W3C versions doesn't add inter-spec links. *** This bug has been marked as a duplicate of bug 12510 ***