Closed Bug 1578863 Opened 7 years ago Closed 7 years ago

Block video autoplay feature seems to fail to block if there is more than one video source on page

Categories

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

69 Branch
defect
Not set
minor

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: u646393, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

Browsed news articles on Yahoo News and saw that the recently added block video autoplay feature fails to block the second video from autoplaying. Example article:
https://www.yahoo.com/lifestyle/teen-boy-goes-blind-after-only-eating-pringles-white-bread-pork-and-french-fries-193653729.html

Actual results:

For news pages that have more than one video source (some Yahoo News article pages have one video at the top of the page and then one unrelated video right above the comments section) the first video on page is stopped from autoplaying but the second starts autoplaying when user scrolls down the page. In very few circumstances no video is blocked from autoplaying.

Expected results:

Both videos should have been blocked from autoplaying. The older feature (block sound) works great though, it blocks sound from media sources 99% of the time.

Severity: normal → minor

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Audio/Video: Playback
Product: Firefox → Core

Alastor, could you take a first pass triage on this one?

Flags: needinfo?(alwu)

The video won't be allowed to autoplay via scrolling, so I guess you have clicked somewhere on the page or pressed any keyborad key before the second video starts?

Our new autoplay policy would stop all video in the page if the page hasn't been activated by user gestures (mouse click, keyborad press), but once the page has activated by user gesture, it gives page a permission to start autoplay.

If you want to use the old blocking autoplay policy, which is only allowing autoplay by clicking, you can set the pref "media.autoplay.enabled.user-gestures-needed" to false, then you can use the old one. However, because of some techinical issue from DOM user input propagation, it still has a compatible issue which would break some websites.

Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(alwu)
Resolution: --- → WORKSFORME

"Our new autoplay policy would stop all video in the page if the page hasn't been activated by user gestures (mouse click, keyborad press), but once the page has activated by user gesture, it gives page a permission to start autoplay."
Makes sense.

"If you want to use the old blocking autoplay policy, which is only allowing autoplay by clicking, you can set the pref "media.autoplay.enabled.user-gestures-needed" to false, then you can use the old one."
I have done so. Thank you for your help!

You need to log in before you can comment on or make changes to this bug.