|Summary:||postMessage() spec now supports sending arrays of ports|
|Product:||WebKit||Reporter:||Andrew Wilson <atwilson>|
|Version:||528+ (Nightly build)|
|OS:||OS X 10.5|
|Bug Depends on:|
Description Andrew Wilson 2009-07-01 13:43:59 PDT
Currently, the various flavors of postMessage (DOMWindow.postMessage, MessagePort.postMessage, Worker.postMessage, etc) take a single optional MessagePort argument which is passed to the destination via the MessageEvent.messagePort attribute. The HTML5 spec has changed to allow passing an array of ports instead, and renames MessageEvent.messagePort to MessageEvent.ports. This spec change didn't seem to generate much feedback one way or the other, so I'm not certain whether it's going to stick (we're the first platform to support MessagePorts) but there's no technical reason not to implement it.
Comment 1 Andrew Wilson 2009-08-18 18:01:58 PDT
Splitting this bug into two parts - part 1 will get the WebCore infrastructure working with passing multiple ports around, and part 2 will hookup the JS bindings.
Comment 3 David Levin 2009-08-20 22:51:45 PDT