Autoplay blocking not working since "gestures-needed" removed from about:config
media.autoplay.enabled.user-gestures-needed in the about:config used to block autoplay, but now it's been taken away. So how is it blocked? And why can't this be a setting NOT in the config, since what's available under Privacy and Security has never worked?
Valittu ratkaisu
media.autoplay.enabled.user-gestures-needed =true has been replaced by media.autoplay.blocking_policy =1 If this isn't working then try media.autoplay.blocking_policy = 2
See also:
- [/questions/1293231] Block autoplay being ignored on Firefox 78
- https://drive.google.com/file/d/1Lkk37Vq8YhURxPL7UBVy0CuuZJU62PYQ/view
Kaikki vastaukset (4)
Valittu ratkaisu
media.autoplay.enabled.user-gestures-needed =true has been replaced by media.autoplay.blocking_policy =1 If this isn't working then try media.autoplay.blocking_policy = 2
See also:
- [/questions/1293231] Block autoplay being ignored on Firefox 78
- https://drive.google.com/file/d/1Lkk37Vq8YhURxPL7UBVy0CuuZJU62PYQ/view
Yes, I'm having this same issue as well.. I've always had success setting "media.autoplay.enabled.user-gestures-needed" to "false" for disabling YouTube videos. I thought that feature was great for reading comments on my videos without negatively inflating analytics of adding more views to my content.
I've tried some of the add-ons to block autoplay on YouTube, but many are a mixed bag and not as reliable as manual tweaks in the config.
Edit:
cor-el said
media.autoplay.enabled.user-gestures-needed =true has been replaced by media.autoplay.blocking_policy =1 If this isn't working then try media.autoplay.blocking_policy = 2 See also:
- [/questions/1293231] Block autoplay being ignored on Firefox 78
- https://drive.google.com/file/d/1Lkk37Vq8YhURxPL7UBVy0CuuZJU62PYQ/view
Thanks, I'll give this a try! :)
Muokattu
media.autoplay.blocking_policy = 2 worked for me. Thank you.
Thanks, media.autoplay.blocking_policy = 2 - works perfect on Windows version of Firefox 78.0.1
Mac Note: I recall that Mac versions could use the same type of configuration, but may also require a separate change to another "autoplay" setting. Hopefully, media.autoplay.blocking_policy = 2 will be the only setting you'll need to change.