[MediaControl-OSX] Use 'MediaPlayer' framework for receiveing media keys
Categories
(Core :: Widget: Cocoa, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox70 | --- | unaffected |
firefox71 | - | disabled |
firefox72 | --- | disabled |
firefox73 | --- | fixed |
People
(Reporter: alwu, Assigned: paul.eliot.warner)
References
Details
Attachments
(1 file)
We have already had a patch from bug1251795, and I think that bug is used to implement how to support global media key for web extension, so we should probably separate the native platform implementation from that.
This bug is used to implement catching media key events globally on OSX by using MediaPlayer
framework.
On Windows, we have bug1584542.
On Linux, we have bug1584030.
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Comment 3•5 years ago
|
||
[Tracking Requested - why for this release]:
We will need to ensure that the patches here remove the use of CGEventTapCreate[1]. This has to land in 71 to avoid the scary native dialog reported in bug 1594028.
Reporter | ||
Comment 4•5 years ago
|
||
Does it need to be P1? because the pref "media.hardwaremediakeys.enabled" is off by default, so you don't change it explicitly, we won't create a CGEventTap
and you won't get this problem.
Comment 5•5 years ago
|
||
(In reply to Alastor Wu [:alwu] from comment #4)
Does it need to be P1? because the pref "media.hardwaremediakeys.enabled" is off by default, so you don't change it explicitly, we won't create a
CGEventTap
and you won't get this problem.
If this can be confirmed, then no, it doesn't have to be a P1. Unfortunately, I have been unable to reproduce myself.
Reporter | ||
Comment 6•5 years ago
|
||
We would create the MediaHardwareKeysEventSourceMac
, which uses CGEventTap
, only when the pref is on [1]. So if the issue is caused by using the CGEventTap
, then it would definitely not happen if user keep the default setting.
Comment 7•5 years ago
|
||
I agree that based on code inspection, we shouldn't be running into this by default. I was hoping to get confirmation from someone who is able to reproduce the scary dialog when the pref is on that it does not pop up with the pref turned off. Since this is most likely the case I'm going to lower the priority to P2. :haik, did you say that you were able to reproduce the dialog on your system?
Comment 8•5 years ago
|
||
(In reply to Stephen A Pohl [:spohl] from comment #7)
I agree that based on code inspection, we shouldn't be running into this by default. I was hoping to get confirmation from someone who is able to reproduce the scary dialog when the pref is on that it does not pop up with the pref turned off. Since this is most likely the case I'm going to lower the priority to P2. :haik, did you say that you were able to reproduce the dialog on your system?
Yes, I realized it appears to be triggered by YouTube. I am able to reproduce this by turning on the pref media.hardwaremediakeys.enabled
, restarting the browser, and then visiting YouTube and watching a video such as https://www.youtube.com/watch?v=QgiSModQM7s
.
Comment 9•5 years ago
|
||
If media.hardwaremediakeys.enabled is set to false by default, that there is no end-user UI to activate (apart from about:config) and that there are no plans to do a pref rollout to activate it in the 71 window, then we don't need to track it for 71 release. If I am missing some context, don't hesitate to contact me, thanks.
Comment 10•5 years ago
|
||
Comment 11•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Updated•5 years ago
|
Description
•