Open Bug 1263509 Opened 8 years ago Updated 2 years ago

[meta] [UI Events-code] Investigate KeyboardEvent.code difference between Chromium and Gecko

Categories

(Core :: DOM: Events, defect)

Product:
Core
Component:
DOM: Events
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox48 --- affected

People

(Reporter: masayuki, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: dev-doc-needed, meta, Whiteboard: btpp-active) 

Chromium will ship KeyboardEvent.code in releases.
https://bugs.chromium.org/p/chromium/issues/detail?id=227231#c81

So, we should investigate the difference between Chromium and Gecko and fix the difference or report the issue to Chromium team.
I reported some differences a half year ago, though.
https://bugs.chromium.org/p/chromium/issues/detail?id=542589
On Windows better to compare also to Edge (assuming it has .code).
Edge does not currently have |code| support.

Along with the spec, we're creating manual tests to make browser interop easier to verify, but Moz and Cr are the first 2 with complete and we're shaking out the edge cases.
Whiteboard: btpp-active

Resetting assignee which I don't work on in this several months.

Assignee: masayuki → nobody
Status: ASSIGNED → NEW
Summary: [UI Events-code] Investigate KeyboardEvent.code difference between Chromium and Gecko → [meta] [UI Events-code] Investigate KeyboardEvent.code difference between Chromium and Gecko
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.