[Bug 24044] How do browsers decide combining character from non-combining character at computing .key value of dead key? from bugzilla@jessica.w3.org on 2013-12-11 (public-webapps-bugzilla@w3.org from December 2013)

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

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

--- Comment #1 from Travis Leithead [MSFT] <travil@microsoft.com> ---
What is the non-combining character that the OS provides to browsers? 

We could alternatively have the .key value be "DeadKey" for any dead key...
might simplify things.

We also have to decide what compositionupdate.data will be during the dead key
sequence.

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

Received on Wednesday, 11 December 2013 01:26:29 UTC