Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)

(Sorry for the delay to reply, I lost notifications during catching COVID-19 in early this month.)

> Based on this, Firefox is not correct to include unmatched surrogates.

Oh, yeah, it's just a bug.
* https://searchfox.org/mozilla-central/rev/0ddb7a38cdbba30df8f19549f678a22fa16967d1/editor/libeditor/HTMLEditor.cpp#1458-1459
* https://searchfox.org/mozilla-central/rev/0ddb7a38cdbba30df8f19549f678a22fa16967d1/editor/libeditor/TextEditor.cpp#320-323,325-326

Those handlers should refer `KeyboardEvent.key` value instead. I'll fix it.

From my experiences, if it'll be standardized, only one behavior should be defined. E.g., UI Events has non-normative explanation about `keyCode` and `charCode` values of `keypress`, that defines 2 models, but now Firefox aligned the model from the split model to the conflated model because of compatibility with the other browsers. Therefore, defining minor browsers' behavior may just make the developers confused, and all browsers should take same behavior in any OSes if it's possible.

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

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