Open
Bug 1186125
Opened 9 years ago
Updated 2 years ago
Spec defines `which` property on KeyboardEvent, not UIEvent
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
NEW
People
(Reporter: jdm, Unassigned)
Details
We're all over the place here.
Spec for UIEvent: https://w3c.github.io/uievents/#interface-UIEvent
KeyboardEvent with `which` property: https://w3c.github.io/uievents/#KeyboardEvent-supplemental-interface
MDN documentation for MouseEvent.which: https://developer.mozilla.org/en-US/docs/Web/API/MouseEvent/which
MDN documentation for UIEvent.which (missing): https://developer.mozilla.org/en-US/docs/Web/API/UIEvent
mozilla-central UIEvent.which: http://mxr.mozilla.org/mozilla-central/source/dom/webidl/UIEvent.webidl#34
mozilla-central MouseEvent.which: http://mxr.mozilla.org/mozilla-central/source/dom/events/MouseEvent.h#39
So far there seems to be at least one piece of web content that could be impacted by making Gecko follow the spec here: https://github.com/servo/servo/issues/6643#issuecomment-122768111
Olli, what are your thoughts here? Should we try to get this removed from Gecko?
Comment 1•9 years ago
|
||
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27558 is still open, so it is a bit unclear what will happen.
Reporter | ||
Comment 2•9 years ago
|
||
The consensus in https://github.com/w3c/uievents/issues/35#issuecomment-193106296 suggests that UIEvent.which is the ideal.
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•