3 ms·
I don't know if it is surfaced in about:preferences, but I know the functionality exists in Firefox 53 at least, since that's what I'm using now (32-bit 53.0.3,
by throwanem 9y ago
I don't know if it is surfaced in about:preferences, but I know the functionality exists in Firefox 53 at least, since that's what I'm using now (32-bit 53.0.3, Windows).
In about:config, look for media.block-autoplay-until-in-foreground.
- maxxxxx 9y agoThey really need to work on usability for the regular end user if they want to succeed. So many useful settings are buried deep down in about:config. The auto play settings should be super accessible.
- throwanem 9y agoI agree. On the other hand, at least it doesn't take installing an extension, the way it apparently does in Chrome and Opera. (Safari, too? Webkit seems the common thread here.) Failing to surface it to the user is an odd decision, but perhaps still preferable to what's apparently the typical alternative.
- JosephLark 9y ago> at least it doesn't take installing an extension, the way it apparently does in Chrome and Opera Eh? This has been default in Chrome for ages based on my experience. I was actually surprised that it wasn't the default behaviour on FF when I made the switch a couple months back.
- throwanem 9y agoOh, I see that it is - I'm mixing up "disable autoplay until tab is focused" and "disable autoplay, period". Apologies for the confusion, and thanks for the catch! I'd edit my prior comment to remove the error, but that would make this subthread incomprehensible, so I'll leave it as it stands.
- maxxxxx 9y agoThis would be an easy way to show a real benefit to the end user. All I hear from them is stuff about memory or JavaScript performance. I just don't know why I should recommend Firefox to my mom. They really seem to be forgetting the common user.
- jacquesm 9y ago> I just don't know why I should recommend Firefox to my mom. Because it is not made by an advertising agency. > They really seem to be forgetting the common user. No, they have less budget to work with. But they're doing pretty good.
- asadotzler 9y agoThe autoplay disabling isn't ready yet and that's why it's still behind an about:config flag.
- maxxxxx 9y agoI don't know the internals of Firefox but this should be relatively easy to do and have real benefit to the user. Squeezing out 30 percent from from JavaScript doesn't make that much of a difference in comparison.
- throwanem 9y agoSurfacing "disable autoplay until tab is focused" benefits those users who care about it. Improving Javascript performance by 30 percent benefits everyone.
- maxxxxx 9y agoI think a lot of people care about ads autoplaying and making sound.
- tolien 9y agoIt's also unlikely to be worked on by the same group of developers, so this is of the "why don't you do x instead of y" class of comment, where x = {fix media playback,cure Ebola} and y={make JS run faster,send things into space}.
- throwanem 9y agoUnready in what way, if you don't mind my asking? I haven't seen it misbehave yet, although I grant that's n=1.
- cpeterso 9y agoSome buggy video players are broken when the browser doesn't autoplay "autoplay" video because the player's play/pause state doesn't match the browser's. Firefox developers are looking at workarounds like telling the player the video is playing, but not downloading the video. You can set about:config pref "media.autoplay.enabled" = false to test. YouTube used to be broken. I don't know if it still is.