Closed Bug 1550477 Opened 2 years ago Closed 2 years ago

Blocked media starts on any interaction with page

Categories

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

68 Branch
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: v.p.andronache, Unassigned)

References

()

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0

Steps to reproduce:

Went to espn.com. Clicked on http://www.espn.com/nhl/story/_/id/26705410/avs-captain-takes-blame-controversial-no-goal.

Actual results:

When I got to the page, the video at the top of the page showed the play button. As soon as I interacted with the page, the video started playing. That included trying to clicking on the side to scroll down or clicking on the article text. My ubuntu uses Firefox 66, but I also downloaded 68.0a1 (2019-05-09) (64-bit) and the behavior was the same. The video was not muted.

Expected results:

The video should not have started unless the video itself was clicked.

If I understood correctly, this is Invalid according to bug 1539319, comment 2.

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

Clicking the link activates the document which would allow a site to autoplay. We only block autoplay before user gesture activates the docuement.

If you would like to disable user-gesture model, try to set the pref media.autoplay.enabled.user-gestures-needed=false, which would use click-to-play to block autoplay, but it won't work for all websites.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX

Just a quick question to see if I understand the behavior: if a page is reached by an address being typed in, embedded media will not autoplay, but if it is reached through a click, it will?

And thank you for the user-gestures-needed - I had the flag backwards. I thought 'true' would use click-to-play.

Just a quick question to see if I understand the behavior: if a page is reached by an address being typed in, embedded media will not autoplay, but if it is reached through a click, it will?

If a page is reached by typing an URL, the page you visited is a new document which user hasn't activated yet, so we won't allow autoplay to start.

However, in your case, clicking the link on ESPN, they use the same document for the navigation, so even if you see the new page, the document is still the same one which you has interacted with in the previous page. That is why the autoplay was allowed to start.

Thank you for the explanation - much appreciated.

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