Re: [w3c/uievents] Redefine when `keypress` event should be fired (#266)

> It feels like this should be generating an `input` event rather than a `keypress` event. Since `keypress` is deprecated, we can't ask people to rely on it.

I strongly disagree on this point. IMO, the spec should require what browsers need to implement in order to make web pages work as intended. @masayuki-nakano cited a web compat requirement. If the spec requires something different from what browsers need to implement to be compatible with the web, then the spec will be ignored.

I think this is a fundamental principle for web specs.

Things can be marked as deprecated or obsolete and still have non-optional, well-defined and web-compatible specification.

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

Message ID: <w3c/uievents/issues/266/1887917756@github.com>