[Bug 21137] Define key names for game controller of Android

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21137

--- Comment #3 from Glenn Maynard <glenn@zewt.org> ---
(In reply to comment #2)
> I believe that D3E spec should define key names which will be used in major
> platforms as far as possible because if it wouldn't define them clearly,
> it'd be possible each UA vendors to give different names for same key.
> 
> If this is wrong, the ".key" approach is failure since it allows different
> key names, which means ".key" is not web developer friendly.

What does "GameButtonX" mean?  On a PSX controller, the button labelled "X" is
in the bottom-left, and is usually a primary control.  On a 360 controller,
it's the top-left button and is usually a secondary input.  On whatever input
device Android is exposing, it might mean something completely different. 
Saying that "GameButtonX" maps to "KEYCODE_BUTTON_X on Android" doesn't give a
useful definition on anything that isn't Android.

Being told "the user pressed GameButtonY" doesn't tell the web developer
anything.  It doesn't even mean "pushed a button with a Y on it"--it might be a
controller with PSX labels, which has symbols rather than letters.

(For that matter, why are gamepad controllers being mapped like keys?  They
should be exposed with a joystick API, not generate key events.)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 5 March 2013 00:35:23 UTC