448910 - Support multimedia keyboard for <video> and <audio>

Status: RESOLVED DUPLICATE of bug 1572869

(Toolkit :: Video/Audio Controls, enhancement)

Description

[Biju]

Bug 422538 implemented Ogg Theora backend for <VIDEO> tag
but if press Play/Pause, Stop, Rewind, FF keys on my multimedia keyboard there is no effect of <VIDEO> tag playback.

Mozilla should support those keys.

Comment 1

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

Which OSes support multimedia keys? Maybe all?
Anyway, on Windows we dispatch command events for back/forward/home/search etc. and those events are handled in browser UI.
The list could be extended to support play/pause/etc. ,right Ere?

Though, I'm not sure how to target some specific <video>; what if the page
has several <video>s, should all those get paused, or only the one which
has focus (but <video> doesn't necessarily have a focus usually)

Comment 2

[Ere Maijala (slow)]

No problem in the widget side of things. Currently we post nsCommandEvent for back, forward, reload, stop, search, bookmarks and home. The list can be easily augmented, but something deeper in there needs to make the decision on what to do with the event. I can add those right away when the corresponding atoms have been added to nsWidgetAtomList.h. List of possible commands can be found at <http://msdn.microsoft.com/en-us/library/ms646275(VS.85).aspx>. At least one thing to note is that there might be discrete play and pause buttons or they could be combined to a play/pause button, so both cases should be taken into account.

Comment 5

[Justin Dolske [:Dolske]]

One thing to figure out here is when the media keys should be handled by Firefox vs the OS (assuming the app has some say in that).

The extremes seem fairly obvious:
* When on a tab with no media elements, I expect media keys to control what iTunes is playing in the background (as they do today).
* When watching a full-screen video in Firefox, I'd expect the media keys to control the video being played.

But if there's just a media element (focused or not? scrolled out of view or not?) in a normal tab, what should happen?

Comment 6

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Using content command event is better than app command event.

Comment 7

[Asa Dotzler [:asa]]

Chrome 73 will support multimedia keys for "play," "pause," "previous track," "next track," "seek backward," and "seek forward."

Comment 8

[Alastor Wu [:alwu]]

FYI, supporting hardware media keys is tracking in bug1572869, now we have implemented it on OSX, and will implement it on other platform as well.