[Webkit-unassigned] [Bug 36364] KeyboardEvents -- standards-compliant behavior

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=36364


Alexey Proskuryakov <ap at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ap at webkit.org




--- Comment #1 from Alexey Proskuryakov <ap at webkit.org>  2010-03-19 08:47:12 PST ---
It's not correct that keypress is always a consequence of keydown. On Windows,
any process can send a WM_CHAR message to the browser, which will result in
only keypress being dispatched.

Generating a keypress from a programmatically created keydown is technically
possible, but it would introduce lots of unexpected edge case behaviors. That's
because we'd need to call back into OS keyboard event handling code to process
the raw keydown. On different OSes, we'd get some or all of issues:

- it would be possible to control the browser by dispatching e.g. Cmd+Q;
- event queue would be out of sync, so stateful input methods (inline input, or
just dead keys for plain keyboards) will be confused;
- since processing a raw keydown with an input method frequently pops up
additional UI elements, and runs a nested event loop, we'd get stuck in these.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.