[w3c/uievents] Specify the `textInput` event (Issue #353)

Chromium and WebKit support a `textInput` event, which is similar to `beforeinput`. Firefox doesn't support it (yet), but this is a common web compat issue, so we plan to implement it.

Bugs:
- https://bugzilla.mozilla.org/show_bug.cgi?id=903746
- https://bugs.chromium.org/p/chromium/issues/detail?id=701480
- https://bugs.webkit.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&list_id=9349913&product=WebKit&query_format=advanced&short_desc=textinput%20event&short_desc_type=allwordssubstr

IDL:
- https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/events/text_event.idl
- https://github.com/WebKit/WebKit/blob/main/Source/WebCore/dom/TextEvent.idl

One interop difference I've found so far is the order of events. Demo: https://software.hixie.ch/utilities/js/live-dom-viewer/saved/11385

- Chrome: beforeinput is fired first, then textInput.
-  Safari: textInput is fired first, then beforeinput.


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

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