1394443 - Video starts autoplaying in background while media.block-autoplay-until-in-foreground is true

Status: RESOLVED DUPLICATE of bug 1394455

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

Description

[areendre]

Attachment: 2017-08-28.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20170828100127

Steps to reproduce:

Update to newest Nightly
Open a video in new tab (youtube, and other sites)
Video starts playing in background


Actual results:

Video starts autoplaying in background


Expected results:

Video should not have started playing in the background

Comment 1

[Marius Coman [:mcoman], Ecosystem QA]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Firefox: 57.0a1, Build ID: 20170828100127

I have tested this issue on the latest Nightly (57.0a1) build and could not reproduce it, by strictly using the steps provided in the description. However if I hover the tab with the mouse cursor, playback starts.

Considering this, using the Mozregression tool, I have managed to find a regression window. 

Last good revision: 942d868646cf915a51ce5c5f6c61d6c43e3c17db
First bad revision: 5c705cc6d5708d24e9f6648ca537bf110e62f305
Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=942d868646cf915a51ce5c5f6c61d6c43e3c17db&tochange=5c705cc6d5708d24e9f6648ca537bf110e62f305

From the pushlog, it seems that the bug 1390143 has caused this.

Cervantes, can you please take a look at this?

Comment 2

[Cervantes Yu [:cyu] [:cervantes]]

It shouldn't be bug 1390143 that caused this bug because bug 1390143 only changes code that generates minidumps on browser hangs, nothing related to media playback.

I tried to reproduce this bug and found that the STR in comment #0 doesn't reproduce the bug on the latest nightly. After opening a youtube video in background, it doesn't play automatically. You need to *hover* on the tab to trigger the bug. With this STR I didn't find revision 5c705cc6d5708d24e9f6648ca537bf110e62f305 to have this bug. So it should some other revision that caused this bug. Please rerun mozregression to find the real changeset.

Comment 3

[Marius Coman [:mcoman], Ecosystem QA]

I've rerun Mozzregression and I have managed to find a new regression window:

Last good revision: a3f57d191ae26e1357d681730998688514722855
First bad revision: 51ae9cd5f5130686b226cb06b862ef37d1604c4c
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a3f57d191ae26e1357d681730998688514722855&tochange=51ae9cd5f5130686b226cb06b862ef37d1604c4c

It seems to have been caused by bug 1385453. However, I'll close this as Resolved-Duplicate because I have found a few other bugs that are the same.

Comment 4

[Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/reply/question/etc.)]

clearing per dupe