- From: Doug Schepers <schepers@w3.org>
- Date: Fri, 27 Aug 2010 00:57:48 -0400
- To: "Hallvord R. M. Steen" <hallvord@opera.com>
- CC: www-dom@w3.org
Hi, Hallvord- Thanks for the keen eye. We are transitioning to Last Call, but we can address these issues during LC. Regards- -Doug Schepers W3C Team Contact, SVG and WebApps WGs Hallvord R. M. Steen wrote (on 8/11/10 7:06 PM): > Hi, > referring to 6.2.3 second example: this is not what browsers actually do > per my testing. > > ^ and q will cause two different keypress (and/or textInput) events, one > for the circumflex and one for the base character. The keydown for the > incompatible base character triggers two keypress events, first the one > "inherited" from the dead key, then the base character. Hallvord R. M. Steen wrote (on 8/11/10 11:17 PM): > Under point 6.2.5 the text after the second example contains: > > "If the key is part of a sequence of several keystrokes, whether it is a > dead key or it is contributing to an Input Method Editor sequence, the > keystroke shall be ignored (not taken into account) only if the default > action is canceled on the keydown event." > > How is an implementation supposed to "ignore" a dead key? > > The example which follows seems to contradict that text, since it shows > the dead key (though cancelled) modifies the subsequent character. I > think the example is correct (because the OS will be processing the > character before sending the result to the implementation), but the text > is confusing and should perhaps be removed. >
Received on Friday, 27 August 2010 04:57:50 UTC