Incidentally, I browse Twitter while logged in, but the autoplay settings are "per-browser", and Firefox's anti-fingerprinting mode makes Twitter think you're using a new browser on each visit, and thus keeps autoplaying all the time without the above setting. Pretty irritating.
media.autoplay.default = 5
media.block-autoplay-until-in-foreground = false
Of course, if you're using Android, about:config isn't an option unless you use nightly.
* media.autoplay.default = 5
* media.autoplay.enabled = false
in my about:config but media.block-autoplay-until-in-foreground was left at its default "true" value, so I changed that.
I am going to post this and restart the browser to see if that did the trick.
*Update*: No, it didn't. sigh
I found this: https://support.mozilla.org/en-US/questions/1274056
> media.autoplay.allow-extension-background-pages false
> media.autoplay.block-event.enabled true
> media.autoplay.block-webaudio true
> media.autoplay.default 5
> media.autoplay.enabled.user-gestures-needed false
There is also this https://old.reddit.com/r/firefox/comments/h0rsd9/could_someo...
> media.autoplay.blocking_policy = 2
seems to correspond to the media.autoplay.enabled.user-gestures-needed setting above. Will try those next.
*Last Update*: I have set:
media.autoplay.allow-extension-background-pages = false
media.autoplay.block-event.enabled = true
media.autoplay.block-webaudio = true
media.autoplay.default = 5
media.autoplay.blocking_policy = 2
and that finally seems to have restored the behavior I want.
Edit: my config is approximately the same, so I apologise for not specifying them more thoroughly. Doing so with one finger and no copy/paste is onerous.
1. Youtube requires two taps to activate video
2. Some news media videos, eg CNN, do not play. *This may result from adblocking; not sure and not motivated to pursue it.
Not really. The mozilla wiki says:
>The technical detail for this policy is that the play invocation should be triggered inside an user input event handler.
If the autoplay is what OP described (ie. "starting to auto-play just by scrolling into view"), then that would satisfy the condition because it's within an user input event handler (the scroll).
> For example, when a user clicks the element X, then we only allow a website to start the element X from a function that is in the call stack based on the X's “click” event handler.
I could be misinterpreting this, but doesn't that imply that scrolling into view would generally not be sufficient to allow autoplay? Since the scroll event would be on the body/window, and the video itself is not the target of the event?