Bug 111824

Summary: Inconsistency on onkeydown, onkeypress, onkeyup events fired
Product: WebKit Reporter: Jose Lejin PJ <jose.lejin>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: ap
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Sample html test file none

Jose Lejin PJ
Reported 2013-03-07 23:09:16 PST
This is about onkeydown, onkeypress, onkeyup events fired in HTML page by a key stroke. Please refer attached sample page KeyEvent.html In different browsers behavior on these events are different. Chrome fires onkeydown, onkeypress, onkeyup events on visible character stroke and onkeydown,onkeyup on other key stroke. IE fires onkeydown, onkeypress events on visible character stroke and only onkeydown on other key stroke. On safari behavior is same as Chrome except, load the page and press enter on address bar, it fires just onkeyup (Once focus is on page and do key stroke, behavior is same as Chrome.)
Attachments
Sample html test file (506 bytes, text/html)
2013-03-07 23:11 PST, Jose Lejin PJ
no flags
Jose Lejin PJ
Comment 1 2013-03-07 23:11:23 PST
Created attachment 192154 [details] Sample html test file
Alexey Proskuryakov
Comment 2 2013-03-11 12:41:55 PDT
What is the bug you would like fixed? WebKit behavior is intentional. The difference between Safari and Chrome is more of an application issue, so it's outside the scope of webkit.org. I'm surprised that you don't get keyup events in IE in your testing, I'm pretty sure I've been seeing them the last time I tried.
Jose Lejin PJ
Comment 3 2013-03-11 22:02:21 PDT
I tested is on IE 8. You can try opening on attached html page in IE. Didn't observe onkeyup event. Anyway IE behavior is out of scope here. If the difference between Safari and Chrome is more of an "application issue", this bug can be terminated. Not applicable to webkit !
Alexey Proskuryakov
Comment 4 2013-03-11 22:24:07 PDT
OK, thank you for the clarification.
Lucas Forschler
Comment 5 2019-02-06 09:19:11 PST
Mass move bugs into the DOM component.
Note You need to log in before you can comment on or make changes to this bug.