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

Is most of the initKeyboardEvent usage in libraries? If it's only a few places generating most of the usage, then we can have them switch to "new KeyboardEvent" and then deprecate.

When I've attempted to use initKeyboardEvent in Chrome, it didn't work as I expected. I couldn't set `keyCode` or `charCode` and I needed to fall back to using "new Event" and setting the fields manually.

I'd prefer to deprecate initKeyboardEvent if possible, but if we can agree on un-deprecating then I'm fine with that.

-- 
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-274996375