1358211 - Blocking autoplay for background tabs (bug 1308154) is breaking twitter videos

Status: RESOLVED WORKSFORME

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

Description

[Caspy7]

I've experienced this on Beta 53 an Aurora 54.

1) create a fresh profile (may not be explicitly necessary)
2) ensure media.block-autoplay-until-in-foreground is set to true
3) open a twitter video (such as https://twitter.com/HollyweedMemes/status/854499913543159808 ) in a background tab
4) wait a full minute (not sure exactly, but 20 seconds is not long enough)
5) select the tab

Expectation:
The video plays.

Reality:
The video area displays: The media could not be played.

I see this frequently when sending video tweets from my phone.

Comment 1

[Blake Wu [:bwu][:blakewu]]

I can repro this bug on my Macbook Pro with the latest nightly(55.0a1). The symptom is like Bug 1348326.

Comment 2

[Caspy7]

Attachment: Twitter Video cannot play.

We should get these higher visibility issues squished before releasing this feature.

Here's a screenshot in case it makes it more compelling for folks.

Comment 3

[Alastor Wu [:alwu]]

It looks like Twitter's bug, it can also be reproduced on Chrome(57.0.2987.133), Safari(9.1) in OSX.
Please also consider to contact with Twitter for reporting this issue.

Comment 4

[Blake Wu [:bwu][:blakewu]]

That's super fast response! 
Sweet. I will report this bug to them.

Comment 5

[Blake Wu [:bwu][:blakewu]]

Hi drichards,
Can you help us check this bug? It seems a Twitter bug.

Comment 6

[Caspy7]

drichards, in case you are unfamiliar with advanced flags in Firefox, for step #2 of my instructions, type about:config in the URL bar and hit enter. Then you can search for and toggle prefs.

As mentioned above though, similar functionality is already enabled and testable on Chrome and Safari.

Comment 7

[drichards]

Confirmed that this is a Twitter bug and not specific to Firefox. No ETA yet on a fix, but we'll look into it.

Comment 8

[Caspy7]

I have tested the steps on a couple of Twitter videos in both Firefox and Chrome and the issue seems to have been resolved so closing this bug.

Feel free to reopen if you cannot reproduce or you have some objection.