postMessage() / webkitPostMessage() are defined as follows in MessagePort.idl: [Custom] void postMessage(in DOMString message, in [Optional] Array messagePorts) [Custom] void webkitPostMessage(in DOMString message, in [Optional] Array transfer) According to the spec (http://www.w3.org/TR/html5/comms.html#messageport), the first argument should be of type 'any', not 'DOMString'. We currently don't notice the issue cause we provide custom implementation for those methods and the custom implementation handles the first argument as being of type 'any'. We should however update MessagePort.idl to avoid confusion.
Created attachment 159419 [details] Patch
Comment on attachment 159419 [details] Patch The change looks reasonable. DedicatedWorkerContext.idl already uses 'any' for postMessage() and webkitPostMessage(). > We currently don't notice the issue cause we provide custom implementation for those methods and the custom implementation handles the first argument as being of type 'any'. Note: Code generators do not yet support 'any', so we can use 'any' only for custom implementations. We want to fix it.
Comment on attachment 159419 [details] Patch Clearing flags on attachment: 159419 Committed r126040: <http://trac.webkit.org/changeset/126040>
All reviewed patches have been landed. Closing bug.