[
https://issues.apache.org/jira/browse/CB-11301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-11301:
----------------------------
Priority: Minor (was: Major)
Key events have been screwed up ever since we decided to do third party
webviews, because it's unclear who owns what key event, and how the key events
map. The good news is that you can at least hook into this with a third-party
plugin, but the bad news is that keypads, headphones and other peripherals get
a lower priority because testing will be INSANE with different hardware combos,
so while we could throw something over the fence, we don't because we get
burned pretty hard when we do that.
> Android Media Buttons only signalled after release
> --------------------------------------------------
>
> Key: CB-11301
> URL: https://issues.apache.org/jira/browse/CB-11301
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Android
> Reporter: Ruediger Jungbeck
> Priority: Minor
> Labels: features
>
> The media button (on Android headsets) issue events when pressed or
> released. There is a Cordova plugin that installs a BroadcastReceiver for
> Media Button intents. But this intents occur after the physical button has
> already been released (to distinguish short and long presses). This prevenets
> the use of the media button as a PTT (push to talk) kery. So there should be
> a handling for the media button that is similar to the handling of the
> volumeup/volumedown In onDispatchKeyEvent
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
