13368 2007-04-16 22:59:14 -0700 KeyboardEvent::initKeyboardEvent doesn't match the DOM Level 3 Events spec 2013-04-05 17:11:15 -0700 1 1 1 Unclassified WebKit DOM 523.x (Safari 3) Mac All NEW P2 Normal --- 1 aroben webkit-unassigned ap aroben k.y.sergey syoichi oldest_to_newest 14500 0 aroben 2007-04-16 22:59:14 -0700 Our implementation of KeyboardEvent::initKeyboardEvent doesn't match the DOM Level 3 Events spec. See the spec here: http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-KeyboardEvents-Interfaces See current implementation of the method here: http://trac.webkit.org/projects/webkit/browser/trunk/WebCore/dom/KeyboardEvent.cpp?rev=19579#L66 Our implementation takes 5 booleans representing the state of the 5 modifier keys, while the spec defines the last argument of the method to be DOMString containing a space-separated list of modifier keys. 14501 1 aroben 2007-04-16 23:09:54 -0700 It looks like WebKit is implementing an old version of this method. http://www.w3.org/TR/2003/WD-DOM-Level-3-Events-20030331/events.html#Events-KeyboardEvents-Interfaces contains a definition that matches WebKit's, and it looks like WebKit's method was checked in on 2003-10-20 (http://trac.webkit.org/projects/webkit/changeset/5226) 14410 2 darin 2007-04-17 12:08:54 -0700 We should consider implementing this in a custom way so that both versions work. 66238 3 darin 2008-01-04 16:39:41 -0800 Also, bug 16375 points out that events crated with initKeyboardEvent aren't very good because they will always have a keyCode of 0 and charCode of 0. So any code that looks at keyCode or charCode, including code inside the engine that responds to keyboard events and older legacy JavaScript code, won't work with these events. 66239 4 darin 2008-01-04 16:40:03 -0800 Sorry, I meant bug 16735.