Bug 93017 - javascript: the AltGr key return a 0 value for the keyCode, instead of 225
Summary: javascript: the AltGr key return a 0 value for the keyCode, instead of 225
Status: UNCONFIRMED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: All Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 76988
Blocks:
  Show dependency tree / graph
 
Reported: 2012-08-02 12:30 PDT by Blindauer
Modified: 2013-02-26 03:23 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Blindauer 2012-08-02 12:30:30 PDT 
Currently, there is no way to know if the altGr key is pressed.

Firefox fixed this problem recently in their release 15

This problem affect some javascripts application, like noVNC or guacamole
(https://github.com/kanaka/noVNC/issues/21, http://guac-dev.org/trac/ticket/136 )


The javascript test page is http://guac-dev.org/pub/tests/key-event-test.html

Currently webkit based browsers return a keyCode 0 for the AltGr Key. Firefox, since version 15 return the value 225.

Can a patch be made to return the same value for webkit browsers ?
(The AltGr key isn't the right Alt. It's a key found in most european keyboard layout)

This can be tested on linux mainly. windows users have a similar bug, but I'll open another BR because of the way to emulate AltGr with Alt+ctrl on windows

Emmanuel
Comment 1 Blindauer 2012-08-22 23:00:08 PDT 
anyone on this bug ?
Comment 2 Gavin Barraclough 2012-08-31 17:49:28 PDT 
This bug is in the wrong component, moving to WebKit Misc in the hope it'll pick up the attention of someone who can move it on in the right direction!
Comment 3 Benjamin ANDRE 2013-02-26 03:23:47 PST 
I confirm the bug, and it's quite a problem.
For instance in French keyboards, Altgr is a key modifier required to insert a '@'. Because of this bug we are not able in webkit to detect the insertion of a '@' ...
If this bug could be taken into account...

regards !