1648100 - Enable MediaControl in release

Status: RESOLVED FIXED

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

Description

[Tom S]

What is the plan for enabling MediaControl on release? From my point of view it works well enough and some features like album images could be implemented later. This has been shipping in Chrome for a long while now.

Comment 1

[Tom S]

I know r/firefox is not super representative, but this has been starting to be requested a lot more often.

Comment 2

[Alastor Wu [:alwu]]

Our old plan was enabling media control on Fx80, but due to lacking of the testing resource, we don't have a chace to have a full testing and enough time to fix discovered bugs on Fx80. Therefore, we would let it ride a train with Fx81.

Comment 3

[Alastor Wu [:alwu]]

Attachment: Bug 1648100 - enable media control by default.

We're going to enable media control on Fx81.

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/02f5b24041eb
enable media control by default. r=chunmin

Comment 5

[Atila Butkovits]

https://hg.mozilla.org/mozilla-central/rev/02f5b24041eb

Comment 6

[Tom S]

Nice. I think we should add this to the release notes, do you agree?

Comment 7

[Alastor Wu [:alwu]]

Sure.

Comment 8

[Tom S]

Edit: see below
I was hoping Alastor would fill this out, but I just put this request in so that we don't forget about it.

Comment 9

[Alastor Wu [:alwu]]

Add my version of release note request.

Release Note Request (optional, but appreciated)
[Why is this notable]: Allow user to control media playback via hardware media keys (keyborad, headset) or virtual media control interface (Windows/Linux/Mac Touchbar)
[Affects Firefox for Android]: No, Android firefox is still using their own component, which is unrelated with desktop implementation
[Suggested wording]: not sure, maybe media control?
[Links (documentation, blog post, etc)]: https://bit.ly/321pza2 (but it's little out of date, will update it later)

Comment 10

[Chris Mills [:cmills]]

I'm removing dev-doc-needed from this — seems that this is just the mechanism by which Firefox is able to hook into OS-level media controls to allow web page media to be cntrolled by them. MediaSession is the API that allows developers to customize the behavior, and we've already documented that.

I might just add a note to the main MediaSession API page on MDN to say that such a mechanism is required for MediaSession to work, but let me know if you think anything else is needed here.

Comment 11

[Alastor Wu [:alwu]]

Hi, Chris,
This feature can work even if we don't have MediaSession API. However, having MediaSession API would enhence its ability, eg. setting customize metadata and action handlers.
Thank you.

Comment 12

[Chris Mills [:cmills]]

:alwu thanks for the clarifying note.