[Bug 24044] New: 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

            Bug ID: 24044
           Summary: How do browsers decide combining character from
                    non-combining character at computing .key value of
                    dead key?
           Product: WebAppsWG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM3 Events
          Assignee: travil@microsoft.com
          Reporter: masayuki@d-toybox.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, www-dom@w3.org

At least on Windows and Android, dead key event produces non-combining
character for browsers. On the other hand, current D3E spec requires browsers
setting combining character for dead key event.

For consistency behavior between browsers and all keyboard layouts on all
platforms, browsers need to use same map from non-combining character to
combining character at computing dead key event's .key value. However, perhaps,
nobody can list-up all dead characters all over the world. Therefore, browsers
may fail to convert non-combining character if it's not major language's.

I'm thinking that the simplest solution of .key value of dead key event should
be non-combining character. And for web apps, adding a bool attribute such as
KeyboardEvent.isDeadKey may be useful.

Any suggestions?

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

Received on Tuesday, 10 December 2013 08:49:00 UTC