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

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

--- Comment #3 from Travis Leithead [MSFT] <travil@microsoft.com> ---
> Regarding bug 24044: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24044
> 
> I think the solution is to add the key value "DeadKey" correct?
> 
> <masayuki> A dead key process causes a set of composition events. So, web
> apps can get the inputting value of dead key sequence even if .key value
> is "DeadKey".
> 
> Right. Through the "data" value of the compositionevent objects.
> 
> <masayuki> Therefore, I think that "DeadKey" is simple solution for the issue.
> 
> Me too.
> 
> <masayuki> It's hard to define a mapping table for combining characters <->
> non-combining character...


http://www.w3.org/2014/04/30-webapps-minutes.html

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

Received on Monday, 5 May 2014 20:03:49 UTC