- From: himorin / Atsushi Shimono via GitHub <sysbot+gh@w3.org>
- Date: Sun, 22 Mar 2020 09:47:13 +0000
- To: public-i18n-archive@w3.org
On this issue, a comment on the issue was posted by the WG but not yet replied from i18n For me, it seems clearer state is desired when dead key (combining character) was input with base character which does not have single-character NFC (example uses circumflex accent with "q"). On dead key used, KeyboardEvent.key and CompositionEvent.data are modified for events of base character for normal cases with single unicode character in NFC. Both two are defined to accept characters with combining characters, and this state uses "might be", there is possible uncertainty. So, based on reply from WG, we are better to ask changing to something like, "this process should be aborted when combination is not a single code point in NFC". -- GitHub Notification of comment by himorin Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/307#issuecomment-602172253 using your GitHub account
Received on Sunday, 22 March 2020 09:47:15 UTC