W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2013

[Bug 23257] New: Review Dead Key Examples and Composition Event use in light of recent changes

From: <bugzilla@jessica.w3.org>
Date: Mon, 16 Sep 2013 20:08:01 +0000
To: www-dom@w3.org
Message-ID: <bug-23257-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23257

            Bug ID: 23257
           Summary: Review Dead Key Examples and Composition Event use in
                    light of recent changes
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM3 Events
          Assignee: travil@microsoft.com
          Reporter: travil@microsoft.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, www-dom@w3.org

In section 6.2.3, it shows two examples of how Dead Keys are expected to be
processed. This processing involves the synthetic generation of composition
events. However, in light of Bug 22842, it seems strange now that keydown/up
pairs are still expected to be processed during even these synthetic
composition process for dead keys.

I don't know what the right solution is here, but it might be along the lines
of: 1) Specify the exact synthetic event order in which UA's should dispatch
the composition events, and suppress normal keydown/up pairs during this
process, or 2) drop the synthetic composition events for dead key input (though
I know this is nice for symmetry with other IME processing), or 3) some other
solution?

IE9-11 at the moment does not generate the synthetic composition events. We
treat the dead key press in isolation, but are unable to report the specific
"key" value (e.g., "DeadCircumflex") due to a bug in how Windows manages the
keyboard state in this scenario. We are working through the bug with Windows,
but wanted to raise awareness of the apparent contradiction in the current
spec.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 16 September 2013 20:08:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:21 UTC