Re: [w3c/uievents] Require support for legacy events (Issue #366)

We still want to discourage its use, because there are accessibility issues with `keypress` that `input` has fixed. For example, speech input devices should create an `input` event rather have to create a sequence of `keypress` events appropriate for the current layout/locale. Sites that rely only on `keypress` would work fine for many people, but would effectively block (or require odd hacks for) users with non-standard input devices. This is why we wanted a stronger deprecation message for this event.

I don't think "legacy" is a strong enough phrasing for this since it implies that it's OK to use, but it might go away at some point. I think our position is closer to: "it's somewhat harmful to rely on this event, but we can't remove it".


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

Message ID: <w3c/uievents/issues/366/1905035343@github.com>