Autoplay blocker fails on huffpost.com
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
People
(Reporter: mozillabugs, Unassigned)
Details
The page https://www.huffpost.com/entry/pennsylvania-shell-workers-only-paid-if-attended-trump-speech_n_5d576dd7e4b056fafd0c08db sometimes autoplays audio despite tools/options/Block websites from automatically playing sound being selected with no exceptions.
It's unclear exactly what triggers the page to autoplay. Sometimes scrolling the article appears to do it, while other times clicking in the address bar or switching to a blank tab and back again seems to do it. I will update this bug if I find a more-reliable way to trigger the bug.
I am using FF 68.0.2 Win64.
|
||
Comment 1•6 years ago
|
||
I couldn't reproduce this issue on both Firefox release 68 and Nightly 70 on Mac OS 10.14.
Would you mind to provide your autoplay related prefs to us? In addition, if you click or press keyborad input on the page, it would activate the page and allow the page to start autoplay. I would guess that maybe you accidently clicked on the page, which made autoplay started?
In addition, this kind of autoplay policy is what we call user-gesture-activation, if you would like to have only starting autoplay when clicking, you can set the pref media.autoplay.enabled.user-gestures-needed to false, which will only enable autoplay when you click on certain media element. However, this feature is still experimental, because it won't work for all websites.
|
Reporter | |
Comment 2•6 years ago
|
||
(In reply to Alastor Wu [:alwu] from comment #1)
I couldn't reproduce this issue on both Firefox release 68 and Nightly 70 on Mac OS 10.14.
Would you mind to provide your
autoplayrelated prefs to us?
services.sync.prefs.sync.media.autoplay.default;true
media.block-autoplay-until-in-foreground;true
media.autoplay.enabled.user-gestures-needed;true
media.autoplay.default;1
media.autoplay.block-event.enabled;false
media.autoplay.blackList-override-default;true
dom.media.autoplay.autoplay-policy-api;false
media.autoplay.enabled;false
media.autoplay.block-webaudio;true
media.autoplay.ask-permission;true
media.autoplay.allow-muted;false
media.autoplay.allow-extension-background-pages;false
In addition, if you click or press keyborad input on the page, it would activate the page and allow the page to start autoplay. I would guess that maybe you accidently clicked on the page, which made autoplay started?
That is possible; my (Alps, ick!) touchpad sometimes spuriously generates a click. I will try to reproduce the problem while taking care not to click anything or give any keyboard input. Does this include pageup/down/home/end?
In addition, this kind of autoplay policy is what we call
user-gesture-activation, if you would like to have only starting autoplay when clicking, you can set the prefmedia.autoplay.enabled.user-gestures-neededtofalse, which will only enable autoplay when you click on certain media element. However, this feature is still experimental, because it won't work for all websites.
OK.
|
|
||
Comment 3•6 years ago
|
||
(In reply to mozillabugs from comment #2)
That is possible; my (Alps, ick!) touchpad sometimes spuriously generates a click. I will try to reproduce the problem while taking care not to click anything or give any keyboard input. Does this include pageup/down/home/end?
pageup/down/home/end won't activate the page, we only support printable keys, carriage return and space.
So I will close the bug for now, because it sounds like that document was accidently activated by clicking so that the page started to allow autoplay.
However, feel free to reopen it if you can reproduce this issue again even if you didn't activate a page.
Thank you.
Description
•