[Bug 24044] How do browsers decide combining character from non-combining character at computing .key value of dead key?

• From: <bugzilla@jessica.w3.org>
• Date: Wed, 11 Dec 2013 01:28:13 +0000
• To: public-webapps-bugzilla@w3.org
• Message-ID: <bug-24044-2532-iIgIQwhloN@http.www.w3.org/Bugs/Public/>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24044

--- Comment #2 from Masayuki Nakano <masayuki@d-toybox.com> ---
[10:19] <Travis> Is there a general "combining" key value?
[10:19] <Travis> I suppose we could invent one.
[10:20] <Travis> ... event.key == "DeadKey"
[10:20] <Travis> ... is almost as useful as event.isDeadKey
[10:21] <Travis> But, the compositionupdate event would still need to carry the
combining key value in its data attribute, right?
[10:21] <masayuki> Hmm, yes.
[10:23] <masayuki> I feel strange native platforms give non-combining
character, prehaps for displaying the character, but why web apps need
combining character?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 11 December 2013 01:28:15 UTC