-
abarth@webkit.org authored
https://bugs.webkit.org/show_bug.cgi?id=105910 Reviewed by Kentaro Hara. The vendor-prefixed version of postMessage was never widely used. We've been compiling it out of the Chromium port for a while now and haven't received any reports of compatibility problems. I've done a number of web searches for uses of the API and personally contacted a handful of authors I found using the API, all of whom have now moved to the identical unprefixed API. We've publicied the prefix removal in a blog post: http://blog.chromium.org/2012/11/a-web-developers-guide-to-latest-chrome.html and discussed it on webkit-dev: http://lists.macosforge.org/pipermail/webkit-dev/2012-September/022189.html We've done our diligence, and now we should remove the API from the remainder of the ports. * bindings/js/JSDOMWindowCustom.cpp: * bindings/js/JSDedicatedWorkerContextCustom.cpp: * bindings/js/JSMessagePortCustom.cpp: * bindings/js/JSWorkerCustom.cpp: * bindings/v8/custom/V8DOMWindowCustom.cpp: (WebCore::V8DOMWindow::postMessageCallback): * bindings/v8/custom/V8DedicatedWorkerContextCustom.cpp: (WebCore::V8DedicatedWorkerContext::postMessageCallback): * bindings/v8/custom/V8MessagePortCustom.cpp: (WebCore::V8MessagePort::postMessageCallback): * bindings/v8/custom/V8WorkerCustom.cpp: (WebCore::V8Worker::postMessageCallback): * dom/MessagePort.idl: * page/DOMWindow.idl: * workers/DedicatedWorkerContext.idl: * workers/Worker.idl: git-svn-id: http://svn.webkit.org/repository/webkit/trunk@138646 268f45cc-cd09-0410-ab3c-d52691b4dbfc
b2c9e733