Closed Bug 1166548 Opened 10 years ago Closed 9 years ago

media session tracking bug

Categories

(Core :: Audio/Video: Playback, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1112032
Tracking Status
firefox41 --- affected

People

(Reporter: rillian, Unassigned)

References

()

Details

(Keywords: DevAdvocacy)

WHATWG is developing a 'media session' spec for how to hook up hardware playback controls (play/pause, fwd/rew, headset buttons) to HTML media elements, along with some dom extensions to allow web authors to signal intent. https://mediasession.spec.whatwg.org/ See also https://github.com/whatwg/mediasession#media-session-standard for use cases, motivation, etc.
Anthony, I think we should implement this. At least as far has hooking up the play/pause button. How could we divide the work?
Flags: needinfo?(ajones)
Looks like this feature will have to wait in line.
Flags: needinfo?(ajones)
Component: Audio/Video → Audio/Video: Playback
Hallvord - are you aware of anyone using or wanting to use this spec?
Flags: needinfo?(hsteen)
Hi, Anthony, I would like to use this spec to implement the media-control for the web contents. It's about to display the a user interface and provide hardware-controlling ability, see more details in the behavior of the content kind [1]. [1] https://mediasession.spec.whatwg.org/#media-session-kinds
We had a meeting with a few folks from Mozilla (Platform and Devrel) and developers from a website that lets creators upload and share their music. One of the things we mentioned was that having access to these hardware buttons (or the mapping in Macs etc) would really help in making the web seamless and more on par with native applications. Example: right now if I have a website that is playing music I sometimes want to just stop it and instinctively reach for the play/pause button. Which ends up a) not stopping the music b) launching iTunes. Whereas what I'd like to happen is for the browser to "register" that is the active music app and capture those keypresses. Or something like that. Until this is possible, music services inside the browser will still have that barrier that keeps them being "a website", and not a normally capable application. Hope that helps :-)
A couple of other people answered this :)
Flags: needinfo?(hsteen)
Work seems to have started on this over in bug 1112032.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.