[prev in list] [next in list] [prev in thread] [next in thread] 

List:       konq-bugs
Subject:    [Bug 246097] window.event.keyCode may return wrong value
From:       <duke_the_killer () hotmail ! com>
Date:       2010-07-29 14:41:18
Message-ID: 20100729144118.9CF39570C7 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=246097





--- Comment #2 from  <duke_the_killer hotmail com>  2010-07-29 16:41:16 ---
Silly me manually typing it
http://xirc.chez.com/onkeydown.html

Interesting links

Keys IE use for onkeypress
http://msdn.microsoft.com/en-us/library/ms536939(VS.85).aspx

Keys IE use for onkeydown
http://msdn.microsoft.com/en-us/library/ms536938(VS.85).aspx

I just saw W3C changed their wording when it comes to onkeypress between
drafts, http://www.w3.org/TR/DOM-Level-3-Events/#events-keyboardevents
"Whether a keypress contributes or not to the generation of a text event is
implementation dependent."


If we want "onkeypress = inserts character" then last 4 tests should not
trigger it (they output nothing)
I could also add Alt + 1, Ctrl + 1, Alt + Shift + 1 to the test list

Opera and Gecko/Firefox currently behave like Konqueror
Trident/IE and Webkit/Chrome-Safari don't

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konq-bugs mailing list
Konq-bugs@mail.kde.org
https://mail.kde.org/mailman/listinfo/konq-bugs
[prev in list] [next in list] [prev in thread] [next in thread]