Re: [w3c/uievents] Require support or non-support for legacy init*Event (#112)

Yes, the [use counter](https://www.chromestatus.com/metrics/feature/timeline/popularity/868) has been in stable for awhile.  The usage is frighteningly high, so we'd need to do some more serious analysis to try to prove that sites do generally have good fallbacks rather than, for example, relying on UA sniffing to decide which code path to take.  Whether that's worth doing for blink is probably @dtapuska's call.  Certainly the fact that Firefox is getting along more-or-less fine without `initKeyboardEvent` suggests we may have a nice opportunity here.

Is the `KeyboardEvent` constructor already interoperable between latest shipped Safari, Edge, Firefox and Chrome?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/112#issuecomment-257663684