Intent to Deprecate and Remove: MessageEvent.webkitInitMessageEvent()

[Philip Jägenstedt]

Primary eng (and PM) emails

phi...@opera.com

Summary

Remove this from MessageEvent.idl:

webkitInitMessageEvent([Default=Undefined] optional DOMString typeArg,
[Default=Undefined] optional boolean canBubbleArg,
[Default=Undefined] optional boolean cancelableArg,
[Default=Undefined] optional any dataArg,
[Default=Undefined] optional DOMString originArg,
[Default=Undefined] optional DOMString lastEventIdArg,
[Default=Undefined] optional Window sourceArg,
[Default=Undefined] optional MessagePort[] transferables);

Motivation

It is virtually unused, and has an unprefixed replacement.

Compatibility Risk

If used without fallback, would throw an exception.

Alternative implementation suggestion for web developers

Use MessageEvent.initMessageEvent().

Usage information from UseCounter

http://www.chromestatus.com/metrics/feature/timeline/popularity/223

That's consistently at 0%. For comparison, the unprefixed variant is around 0.05%:

http://www.chromestatus.com/metrics/feature/timeline/popularity/222

(I've looked at the generated V8MessageEvent.cpp and verified that UseCounter::PrefixedInitMessageEvent is in fact there, since usage this low is unusual.)

Entry on chromestatus.com and/or MDN

https://developer.mozilla.org/en-US/docs/Web/API/MessageEvent

Requesting approval to remove too?

Yes.

[Eric Seidel]

LGTM.

[Dimitri Glazkov]

LGTM.

[TAMURA, Kent]

LGTM3.

--
TAMURA Kent
Software Engineer, Google

[Anne van Kesteren]

On Tue, May 27, 2014 at 11:14 PM, Philip Jägenstedt <phi...@opera.com> wrote:
> Alternative implementation suggestion for web developers
>
> Use MessageEvent.initMessageEvent().

That is not standardized either. You want to advocate new
MessageEvent(type, init) instead.


--
http://annevankesteren.nl/

[Sigbjorn Finne]

Den 28.05.2014 09:35, skreiv Anne van Kesteren:
> On Tue, May 27, 2014 at 11:14 PM, Philip Jägenstedt <phi...@opera.com> wrote:
>> Alternative implementation suggestion for web developers
>>
>> Use MessageEvent.initMessageEvent().
>
> That is not standardized either. You want to advocate new
> MessageEvent(type, init) instead.
>
>

Definitely; there's https://crbug.com/311332 for that (and this prefixed
appendage.)

--sigbjorn

[Philip Jägenstedt]

On Wed, May 28, 2014 at 9:35 AM, Anne van Kesteren <ann...@annevk.nl> wrote:
>
> On Tue, May 27, 2014 at 11:14 PM, Philip Jägenstedt <phi...@opera.com> wrote:
> > Alternative implementation suggestion for web developers
> >
> > Use MessageEvent.initMessageEvent().
>
> That is not standardized either. You want to advocate new
> MessageEvent(type, init) instead.

Oh, thanks! Unfortunately the usage of MessageEvent.initMessageEvent()
is a bit high still, when was it dropped from Gecko?

Philip

[Anne van Kesteren]

https://developer.mozilla.org/en-US/Firefox/Releases/26/Site_Compatibility
apparently. https://bugzilla.mozilla.org/show_bug.cgi?id=848294 is
where we switched.


--
http://annevankesteren.nl/

[Simon Pieters]

On Wed, 28 May 2014 09:35:05 +0200, Anne van Kesteren <ann...@annevk.nl>
wrote:

> On Tue, May 27, 2014 at 11:14 PM, Philip Jägenstedt <phi...@opera.com>
> wrote:
>> Alternative implementation suggestion for web developers
>>
>> Use MessageEvent.initMessageEvent().
>
> That is not standardized either. You want to advocate new
> MessageEvent(type, init) instead.

Not having it means createEvent('messageevent') doesn't make sense to
have, either, which was recently added to the DOM spec. Also see
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25907

--
Simon Pieters
Opera Software