[Webkit-unassigned] [Bug 16735] keyboard events created with DOM have keyCode and charCode of 0; thus they aren't handled correctly internally

[bugzilla-daemon at webkit.org]

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





--- Comment #22 from Darin Adler <darin at apple.com>  2010-03-18 13:26:02 PST ---
(In reply to comment #21)
> I did not quite follow the whole discussion or dig into the code, but is it
> foreseen that dispatching a "keydown" also fires the corresponding "keypress"
> if the keyIdentifier warrants it (if a visible character is typed as a result
> of the keydown). The standard does not foresee to be able to dispatch
> "keypress" as a separate event, but one should result in the other (if
> preventDefault is not called from a keyDown handler).

Sounds logical but:

    1) Not really the same thing as this bug, so not clear it should be
discussed here.

    2) Does not match other browsers’ behavior so could lead to
incompatibilities.

We tried a while back to have keydown events dispatch keypress events in their
default event handlers but found this is not how any other browser behaves.
Lets discuss this elsewhere, though. There’s already a lot of discussion here.

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