We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
keypress
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:
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
The text was updated successfully, but these errors were encountered:
Input
I think the ideal place to discuss this is upstream: w3c/uievents#346
Sorry, something went wrong.
No branches or pull requests
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
The text was updated successfully, but these errors were encountered: