Open jrandolf-2 opened 1 year ago
In all three browsers, we have inconsistent behavior w.r.t. keypress events with unicode characters that are surrogate pairs.
keypress
Specifically, the following behavior is observed:
The user expectation is probably aligned with Safari's rather than Firefox's, so I propose we align with Safari on this matter.
CC: @whimboo
I think the ideal place to discuss this is upstream: https://github.com/w3c/uievents/issues/346
In all three browsers, we have inconsistent behavior w.r.t.
keypress
events with unicode characters that are surrogate pairs.Specifically, the following behavior is observed:
keypress
events are emitted, one for each surrogate pair.keypress
event is emitted, for the full U32 unit.The user expectation is probably aligned with Safari's rather than Firefox's, so I propose we align with Safari on this matter.
CC: @whimboo