autoplay is not blocked on youtube after in-place internal youtube navigations
Categories
(Core :: Audio/Video: Playback, defect, P5)
Tracking
()
People
(Reporter: bughit.github, Unassigned)
Details
- Fx 67.0.0 x64, win7 sp1 x64, new profile
- start Fx with a new profile
- load a youtube video page directly via the urlbar
- the urlbar shows the play-blocked icon and the video does not play
- click on any video from the "up next"/related column
- after it loads, the urlbar still shows the play-blocked icon, but the new video plays
The new youtube interface is probably required to repro, has to look as it does in chrome.
In the new interface, Internal youtube navigations do an in-place page replacement not a full browser navigation and this is likely needed to manifest the bug.
|
||
Updated•5 years ago
|
|
||
Comment 1•5 years ago
|
||
Duplication of Bug 1540807
This can't possibly be working as designed
- The urlbar still shows the play-blocked icon
- The argument about document activation is a legalistic loophole that completely violates the spirit of this feature
- this click is effectively a navigation to a new page with a new url
- the fact that it does so in-place is an implementation detail the user should not be expected to know or understand
- from the user perspective this is a loading of a new page, the urlbar shows playback is blocked, the user expects playback to be blocked
- but it's not, so a clear bug
please have the designers of autoplay blocking review this and explain why the above is invalid
media.autoplay.enabled.user-gestures-needed=false makes no difference
How can you claim that firefox has an autoplay-blocking feature when it's completely broken on youtube (by far the largest video site)?
Every video click on youtube autoplays, this is precisely what this feature is supposed to prevent.
If you won't address it, at least stop pretending that it exists.
|
||
Comment 4•5 years ago
|
||
(In reply to bughit from comment #3)
media.autoplay.enabled.user-gestures-needed=false makes no difference
How can you claim that firefox has an autoplay-blocking feature when it's completely broken on youtube (by far the largest video site)?
Every video click on youtube autoplays, this is precisely what this feature is supposed to prevent.
If you won't address it, at least stop pretending that it exists.
I couldn't agree more with how flawed this feature is. It's as much use as having a pause feature on a TV box that only pauses for up to one minute before playing again. Imagine how annoying that would be. It's unbelievable that these bug reports are being marked as "invalid" when it's as clear as daylight that this autoplay-blocking feature is flawed.
|
||
Updated•5 years ago
|
|
||
Comment 5•5 years ago
|
||
Hi,
I've tested this using the latest Nightly version 74.0a1 (2020-01-13) (64-bit) for Ubuntu 18.04.3 LTS and I’m able to reproduce the issue. Based on this I will mark firefox74 flag as affected.
Best,
Clara
Mozregression shows this bug goes back to at least July 20th, 2019, but Mozregression crashed at that point and won't restart.
media.autoplay.blocking_policy 2 seems to help. Trying to debug another autoplay seems to have screwed up my settings.
Behavior still incorrect in Firefox 87 and it affects all platforms (can reproduce it on macOS and Linux) as well as all achitectures (can reproduce it on x86 as well as on ARM).
Also I agree with everything said above. The autoplay blocker should work like the pop-up blocker. That is a reasonable expectation and if the pop-up blocker would work as the autoplay blocker currently does, everyone would agree that the pop-up blocker is broken/useless.
Proof of concept:
https://addons.mozilla.org/en-US/firefox/addon/disableautoplay
|
||
Comment 10•2 years ago
|
||
It is WORSE than the initial report in this thread is saying.
In my case, YouTube sometimes starts autoplaying videos since the very beginning, not after any navigations.
The settings for the site for autoplay: "Block Audio and Video".
The issue is, that it is "sometimes", meaning that there is no way to reliably reproduce it.
|
|
||
Comment 11•2 years ago
|
||
I am not sure how it is even possible, considering the fact that FireFox is supposed to block any attempts to initiate playback of any media automatically via generating fake mouse click/key events.
There should not be a JavaScript code that could possibly circumvent this, and yet it is happening for years and Mozilla programmers can not find the bug that allows this.
|
||
Comment 12•2 years ago
|
||
This is an expected behavior for the default blocking policy, and Firefox also provides other blocking policies which can fulfill only allowing only when users click on media. See this for more details.
|
|
||
Comment 13•2 years ago
|
||
Do not call it "Block autoplay" then, if it barely ever blocks anything in reality, and it is by design.
Or at least provide a standard GUI option (not just "media.autoplay.blocking_policy" in "about:config") for the users if they want to ACTUALLY block autoplay or not. The current "solution" is openly user-hostile, misleading.
Thanks in advance.
Description
•