- From: <bugzilla@jessica.w3.org>
- Date: Fri, 01 Nov 2013 07:23:12 +0000
- To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23697 Bug ID: 23697 Summary: KeyboardEventInit in UI Events doesn't include keyCode/charCode/which but in D3E, it includes them Product: WebAppsWG Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: UI Events Assignee: garykac@google.com Reporter: masayuki@d-toybox.com QA Contact: public-webapps-bugzilla@w3.org CC: mike@w3.org, public-webapps@w3.org UI Event defines: > dictionary KeyboardEventInit : UIEventInit { > DOMString char = ""; > DOMString key = ""; > DOMString code = ""; > unsigned long location = 0; > boolean ctrlKey = false; > boolean shiftKey = false; > boolean altKey = false; > boolean metaKey = false; > boolean repeat = false; > DOMString locale = ""; > }; D3E defines: > dictionary KeyboardEventInit { > boolean bubbles = false; > boolean cancelable = false; > AbstractView? view = null; > long detail = 0; > DOMString key = ""; > unsigned long location = 0; > boolean ctrlKey = false; > boolean shiftKey = false; > boolean altKey = false; > boolean metaKey = false; > boolean repeat = false; > DOMString locale = ""; > unsigned long charCode = 0; > unsigned long keyCode = 0; > unsigned long which = 0; > }; UI Events' definition doesn't include charCode/keyCode/which. However, all attributes which are legacy should be able to be initialized at constructing events. # UI Events still have "char", so, I think that UI Events's definition is older than D3E's. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Friday, 1 November 2013 07:23:21 UTC