[webkit-dev] webkitPostMessage

[Adam Barth]

On Sun, Apr 29, 2012 at 12:34 PM, Maciej Stachowiak <mjs at apple.com> wrote:
>On Apr 29, 2012, at 11:01 AM, Adam Barth <abarth at 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 just post a patch.
>
>
> Comparing your post to the recommended steps on that page (the page says the
> same steps should be applied to removing only the prefixed version of a
> feature):
>
> It looks like you did this:
>
> * Any deprecation should be sent to webkit-dev for discussion.

Yes.

> It doesn't look like you did any of these yet:
>
> * Any deprecation requires some data as to why the feature can be deprecated.
> The goal of the data is to show that the feature is not widely used and is
> not popular. The following would qualify:
>
>   * usage statistics in the wild (either by instrumenting the browser or any
> other means).
>   * some discussions on the standard mailing lists underlining that the
> standards' bodies don't think there is enough traction to get the feature
> standardized.
>
>   * some proof that there is others way to achieve the same result that are
> better.

On Sun, Apr 29, 2012 at 12:53 PM, Ryosuke Niwa <rniwa at webkit.org> wrote:
> It appears to me that the the unprefixed version will be a better
> alternative in this case since the websites can just use the same API on all
> spec-compliant browsers if ArrayBuffer is supported in the unprefixed
> version.

Agreed.

On Sun, Apr 29, 2012 at 12:34 PM, Maciej Stachowiak <mjs at apple.com> wrote:
>   * some proof that web-developers don't care much about this feature.
>   * ...
>
> It seems like this hasn't really happened but you did give people due
> notice:
>
> * If several vendors are supporting the feature, we expect people to have
> interacted with them to assess their support towards the removal.
>
> ==> I can add that I'm not aware of any WebKit-specific content at Apple
> that uses webkitPostMessage.

Great.

Thanks,
Adam