I read https://trac.webkit.org/wiki/DeprecatingFeatures, but I'm
still unsure how to proceed with removing webkitPostMessage and
aligning postMessage with the spec. No one responded to my earlier
message, so I'm inclined to just post a patch.
Many thanks,
Adam
On Tue, Apr 10, 2012 at 9:08 PM,
wrt #1, I believe that postMessage implements what is in the spec and
webkitPostMessage additional has support for ArrayBuffers which wasn't in
the postMessage spec yet but was going to be added. If the behaviors from
webkitPostMessage were added to postMessage, then it coudl be removed.
wrt #2,
On Sun, Apr 29, 2012 at 11:15 AM, David Levin le...@google.com wrote:
wrt #1, I believe that postMessage implements what is in the spec and
webkitPostMessage additional has support for ArrayBuffers which wasn't in
the postMessage spec yet but was going to be added. If the behaviors from
On Apr 29, 2012, at 11:01 AM, Adam Barth aba...@webkit.org wrote:
I read https://trac.webkit.org/wiki/DeprecatingFeatures, but I'm
still unsure how to proceed with removing webkitPostMessage and
aligning postMessage with the spec. No one responded to my earlier
message, so I'm inclined to
On Sun, Apr 29, 2012 at 12:34 PM, Maciej Stachowiak m...@apple.com wrote:
On Apr 29, 2012, at 11:01 AM, Adam Barth aba...@webkit.org wrote:
I read https://trac.webkit.org/wiki/DeprecatingFeatures, but I'm
still unsure how to proceed with removing webkitPostMessage and
aligning postMessage
On Sun, Apr 29, 2012 at 12:34 PM, Maciej Stachowiak m...@apple.com wrote:
On Apr 29, 2012, at 11:01 AM, Adam Barth aba...@webkit.org wrote:
I read https://trac.webkit.org/wiki/DeprecatingFeatures, but I'm
still unsure how to proceed with removing webkitPostMessage and
aligning postMessage with
On Apr 29, 2012, at 12:53 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Sun, Apr 29, 2012 at 12:34 PM, Maciej Stachowiak m...@apple.com wrote:
On Apr 29, 2012, at 11:01 AM, Adam Barth aba...@webkit.org wrote:
I read https://trac.webkit.org/wiki/DeprecatingFeatures, but I'm
still unsure how to
On Sun, Apr 29, 2012 at 1:06 PM, Maciej Stachowiak m...@apple.com wrote:
On Apr 29, 2012, at 12:53 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Sun, Apr 29, 2012 at 12:34 PM, Maciej Stachowiak m...@apple.com wrote:
On Apr 29, 2012, at 11:01 AM, Adam Barth aba...@webkit.org wrote:
I read
On Apr 29, 2012, at 1:35 PM, Adam Barth aba...@webkit.org wrote:
There is very little cost on the WebKit project to maintain webkitPostMessage
in addition to postMessage. Instead, supporting webkitPostMessage imposes a
cost on the web platform at large by reducing interoperability
On Sun, Apr 29, 2012 at 2:25 PM, Maciej Stachowiak m...@apple.com wrote:
On Apr 29, 2012, at 1:35 PM, Adam Barth aba...@webkit.org wrote:
There is very little cost on the WebKit project to maintain
webkitPostMessage in addition to postMessage. Instead, supporting
webkitPostMessage imposes
On Apr 29, 2012, at 6:42 PM, Adam Barth aba...@webkit.org wrote:
On Sun, Apr 29, 2012 at 2:25 PM, Maciej Stachowiak m...@apple.com wrote:
On Apr 29, 2012, at 1:35 PM, Adam Barth aba...@webkit.org wrote:
There is very little cost on the WebKit project to maintain
webkitPostMessage in
On Apr 29, 2012, at 6:56 PM, Maciej Stachowiak m...@apple.com wrote:
I think the relevant question is how much (if any) content uses
webkitPostMessage (without unprefixed postMessage fallback). The fact that
postMessage incorporates the new functionality doesn't answer that question.
[+dslomov]
I found a thread on public-webapps that seems related to this
question. Dmitry, do you know what current status is here? I'd like
to make sure we're on a path towards interoperability with other
browsers.
Thanks,
Adam
On Tue, Apr 10, 2012 at 9:08 PM, Adam Barth aba...@webkit.org
I'm trying to understand why we have both DOMWindow.webkitPostMessage
and DOMWindow.postMessage. I'm also trying to understand the
following comment in {JS,V8}DOMWindowCustom.cpp:
// This function has variable arguments and can be:
// Per current spec:
// postMessage(message,
14 matches
Mail list logo
