913048 - supporting key event forwarding from chrome to content

Status: RESOLVED DUPLICATE of bug 989198

(Core :: DOM: Events, defect)

Description

[(inactive after 6/18) Alive Kuo [:alive]]

See https://groups.google.com/forum/#!topic/mozilla.dev.b2g/hd0LGDeiILo

We want to send hardware button event to user apps.
Currently we're blocking the event in gecko:
http://mxr.mozilla.org/mozilla-central/source/b2g/chrome/content/shell.js#392

If we remove this, the user app should be able to catch the events(I'm not sure now), and we may not want the user app to consume the event or we may want to choose the event to be dispatched to app.

One use case is 'engineering mode', it would run in an app but it wants to know the hardware key event so user could know the hardware works correctly.

Another use case is 'dismiss call or alarm when volumeUp/volumeDown is pressed.

Also we need to replace PAGE_UP/PAGE_DOWN with correct VOLUME_UP/VOLUME_DOWN before we fix this. Filing bug.

Comment 1

[Olli Pettay [:smaug][[e-mail]]]

I'm not 100% sure how we want to do this , but one way is to use
extend Serialization/Deserialization we have in nsDOMEvent and in some other events.

But I don't know how we send key events in general currently to content process on b2g.

Comment 2

[Kan-Ru Chen [:kanru] (UTC+9)]

I'd like to take a stab on this.

Comment 3

[Kan-Ru Chen [:kanru] (UTC+9)]

https://groups.google.com/forum/#!topic/mozilla.dev.webapi/xPGXAHEiVmg

Comment 4

[Marcus Cavanaugh [:mcav]]

Would be nice to have this so that Clock can snooze a ringing alarm upon hardware volume press (bug 812692). The only way to do that currently is to hackily listen for changes to the audio.volume.alarm mozSetting.