Closed Bug 1648100 Opened 4 years ago Closed 3 years ago

Enable MediaControl in release


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




81 Branch
Tracking Status
relnote-firefox --- 81+
firefox81 --- fixed


(Reporter: evilpie, Assigned: alwu)




(1 file)

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.

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

Flags: needinfo?(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.

Assignee: nobody → alwu
Flags: needinfo?(alwu)

We're going to enable media control on Fx81.

Pushed by
enable media control by default. r=chunmin
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 81 Branch

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

relnote-firefox: --- → ?
Flags: needinfo?(alwu)
relnote-firefox: ? → ---


Flags: needinfo?(alwu)

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.

relnote-firefox: --- → ?

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)]: (but it's little out of date, will update it later)

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.

Keywords: dev-doc-needed

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.

Flags: needinfo?(cmills)

:alwu thanks for the clarifying note.

Flags: needinfo?(cmills)
You need to log in before you can comment on or make changes to this bug.