Use browsing context to notify tab mute/unmute media
Categories
(Core :: Audio/Video: Playback, defect, P2)
Tracking
()
People
(Reporter: alwu, Assigned: alwu)
Details
Attachments
(1 file)
This bug will use the browsing context to notify content tab to mute/unmute media, instead of using MessageManager.
If we don't do so, we're not able to mute/unmute media in the different process when we we enable Fission, because the current way we use can only notify one process and would cause the media on other process can't be muted/unmuted.
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 1•6 years ago
|
||
This bug will use the browsing context to notify content tab to mute/unmute media, instead of using MessageManager. We would use the top level canonical browsing context to
set the media mute property for the top level window and propagate it to other top level windows in other processes.
If we don't do so, we're not able to mute/unmute media in the different process when we we enable Fission, because the current way we use can only notify one process and would cause the media on other process can't be muted/unmuted.
Comment 3•6 years ago
|
||
bugherder |
Comment 4•6 years ago
|
||
Confirming this issue as verified fixed on Nightly 70.0a1 (2019-07-22) and Nightly 69.0a1(2019-07-04) on Windows 10x64 , macOS 10.14 and Ubuntu 18.04x64. The Mute tab icon is working as expected.
Description
•