- From: Gary Kacmarcik <notifications@github.com>
- Date: Tue, 06 Oct 2015 15:53:17 -0700
- To: w3c/uievents <uievents@noreply.github.com>
Received on Tuesday, 6 October 2015 22:53:46 UTC
Copied from W3C Bugzilla: https://www.w3.org/Bugs/Public/show_bug.cgi?id=23907 ##### Masayuki Nakano 2013-11-25 08:45:34 UTC Even there is beforeinput event, web applications may want to distinguish whether a keydown event causes text input or not at keydown event handler. For example, if web apps wants to implement text editor and their own shortcut keys, if a key event will cause text input, it shouldn't be handled as shortcut key at keydown event. E.g., Ctrl+Shift+2 of Persian keyboard layout causes inputting ZWNJ. https://bugzilla.mozilla.org/show_bug.cgi?id=414130 So, in such case, text input may be preferred rather than kicking shortcut. I'd like to suggest a new attribute KeyboardEvent.inputText as bool. ##### Comment 1 Travis Leithead [MSFT] 2013-12-04 01:49:09 UTC Moving to UIEvents component with permission from opener. We will not address this as part of finishing DOM3 Events. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/18
Received on Tuesday, 6 October 2015 22:53:46 UTC