Intent to unship: KeyboardEvent.initKeyEvent

[Masayuki Nakano]

Summary: This is legacy initializer of KeyboardEvent, but this is
implemented only by Gecko and was dropped even from DOM Level 2 spec.
There is another initiailizer, `initKeyboardEvent`, and in these days,
web developers can use KeyboardEvent constructor for initializing all
attributes with simpler syntax. So, nobody must require this unless
somebody uses web apps which can run only on Gecko.

Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1717760

Standard: N/A

Platform coverage: all

Preference:

DevTools bug: N/A

Other browsers: Nobody has implemented this except us.

web-platform-tests: included into the second patch which tests its type.

Security and Privacy: It is one of the ways to detect Firefox, but other
Gecko specific API can use for same purpose. So, nothing must be changed
in the wild.

--
Masayuki Nakano <masa...@d-toybox.com>
Working on DOM, Events, editor and IME handling for Gecko

[Masayuki Nakano]

On 21/08/10 13:08, Masayuki Nakano wrote:

Preference:

Oops, `dom.keyboardevent.init_key_event.enabled` can re-enable it for a while.

[Masayuki Nakano]

`KeyboardEvent.initKeyEvent` stays there only in addons for a while, but
currently, it'll be unshipped in the web.

The reason is, some addons use it without feature detection like web
content because they can assume specific path runs only in specific browser.

This was done in https://bugzilla.mozilla.org/show_bug.cgi?id=1727024