[Bug 23907] New: How do web apps distinguish if a keydown event causes text input?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 23907] New: How do web apps distinguish if a keydown event causes text input?

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23907

            Bug ID: 23907
           Summary: How do web apps distinguish if a keydown event causes
                    text input?
           Product: WebAppsWG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM3 Events
          Assignee: [hidden email]
          Reporter: [hidden email]
        QA Contact: [hidden email]
                CC: [hidden email], [hidden email]

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.

--
You are receiving this mail because:
You are on the CC list for the bug.

Reply | Threaded
Open this post in threaded view
|

[Bug 23907] How do web apps distinguish if a keydown event causes text input?

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23907

Gary Kacmarcik <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |MOVED

--- Comment #2 from Gary Kacmarcik <[hidden email]> ---
Now tracking as: https://github.com/w3c/uievents/issues/18

--
You are receiving this mail because:
You are on the CC list for the bug.