Open Bug 1263512 Opened 4 years ago Updated 4 years ago

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

Categories

(Core :: DOM: Events, defect)

Product:
Core
Component:
DOM: Events
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
ASSIGNED
Tracking Flags:
Tracking Status
firefox48 --- affected

People

(Reporter: masayuki, Assigned: masayuki, NeedInfo)

References

Details

(Whiteboard: btpp-active) 

Chromium will ship KeyboardEvent.key 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.
On Windows better to compare also to Edge (assuming it has .key).
Edge does not really have |key| support yet.

It does have the |key| attribute and the current W3C spec was based originally on the IE implementation, but there have been many changes to the spec that have not yet been added to IE/Edge.
Whiteboard: btpp-active
(In reply to Masayuki Nakano [:masayuki] (Mozilla Japan) (offline: 4/29-5/8) from comment #3)
> Filed about WM_APPCOMMAND issue on Chromium:
> https://bugs.chromium.org/p/chromium/issues/detail?id=611682

Oops, this report is wrong. It's environment dependent issue. Chromium works fine for those keys. I'll check the key value difference of them later.
Filed a lot of differences...
https://bugs.chromium.org/p/chromium/issues/detail?id=612694
https://bugs.chromium.org/p/chromium/issues/detail?id=612732
https://bugs.chromium.org/p/chromium/issues/detail?id=612736
https://bugs.chromium.org/p/chromium/issues/detail?id=612737
https://bugs.chromium.org/p/chromium/issues/detail?id=612743
https://bugs.chromium.org/p/chromium/issues/detail?id=612749

Looks like that Chrome's KeyboardEvent.key implementation is wrong. It refers scancode rather than virtual key code. Therefore, the implementation is really broken...

Gary, could you stop releasing KeyboardEvent.key in release build?
Flags: needinfo?(garykac)
You need to log in before you can comment on or make changes to this bug.