Closed Bug 1417812 Opened 7 years ago Closed 7 years ago

block-autoplay-until-in-foreground not work for pinned tabs anymore

Categories

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

57 Branch
defect

Tracking

()

RESOLVED INVALID
Tracking Status
firefox57 --- affected
firefox58 --- affected
firefox59 --- affected

People

(Reporter: Akhristenko, Unassigned)

Details

(Keywords: regression, regressionwindow-wanted)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171115095343 Steps to reproduce: set option media.block-autoplay-until-in-foreground to true open some site with media(for example youtube) pin this tab restart firefox Actual results: media content starts playing even if I did not switch to this tab Expected results: media content do not starts playing until i switch to this tab(as it works now in 55 firefox)
Component: Untriaged → Audio/Video: Playback
Product: Firefox → Core
IIRC, it is by design. Mark, Can you help us check it?
Flags: needinfo?(mliang)
Priority: -- → P3
(In reply to Blake Wu [:bwu][:blakewu] from comment #1) > IIRC, it is by design. > Mark, > Can you help us check it? Yes it's expected, pinned tab is a tricky case. If a user pin a visited tab (foreground tab), the autoplay in that tab will not be blocked, and the browser will remember that even if you restart the browser (open a new session). Media will start playing when the pinned tab is loaded in the background. The reason behind this behavior is that users often pin websites such as Gmail, Calendar or Facebook, and they want to hear the notification sounds from those tabs. This behavior allows users to visit those tabs once, and the media from those tabs will remain unblocked even if you restart the browser and haven't visited those tabs yet.
Flags: needinfo?(mliang)
Mark, Thanks for this explanation. I am going to close this bug as invalid.
Hi Akhristenko, Thanks for reporting this issue. This is by design. Please check comment 2.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.