Re: [w3c/uievents] Review whether `key`, `code` etc should be present in legacy `keypress` events (Issue #349)

I don't remember the details, but when we added `key` and `code`, we didn't know which transition would happen first:

* Would devs stop using `keypress` and start using `input`/`beforeinput`
* Would devs stop using `keyCode`/`charCode` and start using `key`/`code`

To hedge against this uncertainty, having defined `key` and `code` values for `keypress` was the safest approach.

However, I don't think we ever had a serious discussion about whether we should purposefully leave these attribute unset in the KeyboardEvent for `keypress`. It was assumed that they would follow the values in the corresponding `keydown`/`keyup` events.

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

Message ID: <w3c/uievents/issues/349/1610125989@github.com>