Closed Bug 1308154 Opened 4 years ago Closed 3 years ago

[meta] Block autoplay media until the tab is visible at first time

Categories

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

Other Branch
defect

Tracking

()

RESOLVED FIXED
Tracking Status
relnote-firefox --- 56+

People

(Reporter: alwu, Assigned: alwu)

References

(Depends on 1 open bug)

Details

(Keywords: meta)

This feature is to avoid user have unexpected autoplay media from the new tab which doesn't be visited before.

We would block such kind of media and it would be resumed automatically when that tab becomes visible at the first time or user press the audio icon on the tab.
Depends on: 1308399
Depends on: 1314220
Depends on: 1318462
Depends on: 1319771, 1319529, 1319526
Depends on: 1320005
Depends on: 1322505
Depends on: 1328058
Depends on: 1328881
Depends on: 1329170
Depends on: 1329179
Depends on: 1330232
Depends on: 1330195
Depends on: 1330644
Depends on: 1330681
Depends on: 1330929
Depends on: 1331317
Depends on: 1335063
Depends on: 1336309
Depends on: 1337232
Depends on: 1337704
Depends on: 1337778
No longer depends on: 1337778
Depends on: 1338137
Depends on: 1338145
Depends on: 1343465
Depends on: 1347758
No longer depends on: 1349201
Added to Fx54 (Aurora) release notes.
Depends on: 1350947
Depends on: 1352014
Depends on: 1347791
Depends on: 1358211
See Also: → 1338259
What's the status of this feature?  This seems to be a super common request from users in various online feedback that I see, and from the list of the dependencies it looks like it's really close, but I'm not sure how much work is left to ship this...

Thanks!
(In reply to :Ehsan Akhgari (needinfo please, extremely long backlog) from comment #2)
> What's the status of this feature?  This seems to be a super common request
> from users in various online feedback that I see, and from the list of the
> dependencies it looks like it's really close, but I'm not sure how much work
> is left to ship this...
> 
> Thanks!

I was not aware of this feature until recently. chsiang dug into testing status and this feature failed QA signoff for 55, so without uplifts it looks like we are on track for 56. While I have some sympathy for how close this seems to be, uplifts into beta must meet a very high bar of urgency and I'm not seeing that here.

needinfo'ing ajones to get his perspective on the work remaining and testing needed to move forward.
Flags: needinfo?(ajones)
Thanks!  FTR I wasn't advocating for it to be forced into beta necessarily, mostly just curious about the current state.  If we can ship it in 56 that's still great.
Add more info. 
Originally this feature failed QA signoff for 55 due to bug 1350947. Per discussion with chsiang last Monday, my team tend not to fix that bug related to Flash since it is too risky and not worth investing resource to support/maintain Flash cases. The main reason to defer this feature to 56 is UX spec has not been finalized yet especially for bug 1347791. If bug 1347791 is not needed, this feature is ready to go. For now, the current status is UX spec is under review and finalization.
Depends on: 1367356
Depends on: 1378105
Duplicate of this bug: 647429
Moved to Fx56 (Beta) release notes.
Flags: needinfo?(ajones)
Depends on: 1387917
Depends on: 1394455
Depends on: 1394118
Feature has been shipped to release channel.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
This "feature" causes facebook notification tones to leak memory in the parent process when facebook is not the active tab.
Depends on: 1478108
Depends on: 1478860
Depends on: 1478869
No longer depends on: 1478860
No longer depends on: 1478108
Alias: block-autoplay-media
No longer depends on: 1478869
You need to log in before you can comment on or make changes to this bug.