Hi Wes, On 2014-08-21, 10:29 AM, Wesley Johnston wrote:
Summary: We've had some complaints at times about videos autoplaying on mobile devices when sites request autoplay. We should be more mindful of users and try to avoid using data if they don't want it. Sites should be doing this for us, but we've encountered pages where that is not the case. I'm proposing that we at least disable this if the audio/video has to be pulled over a (paid?) mobile network. It may, because of the context that phones are used, be something we'd disable on mobile in general. i.e. The bug report mentions someone using their phone in a quiet setting at home. Theres also some power usage concerns that this would help with. The spec allows this explicitly "Authors are urged to use the autoplay attribute rather than using script to trigger automatic playback, as this allows the user to override the automatic playback when it is not desired". Sites (like games) that want to override this could still use scripting to autoplay (and probably already do).
In general, I'm in favour of not autoplaying at all on mobile devices.
Link to standard: http://www.w3.org/TR/html5/embedded-content-0.html#attr-media-autoplay Platform coverage: Where will this be available? Android, Firefox OS Estimated or target release: Aiming for Firefox 35. Preference behind which this will be implemented: Not sure. We already have a boolean media.autoplay.enabled. I think the best thing would probably be to make it a tri-state.pref.
Why is it not sufficient to just set media.autoplay.enabled=false on mobile platforms? (MXR suggests autoplay is enabled on all platforms.) Is the concern that disabling autoplay too widely will lead to widespread scripted-autoplay, reducing user control yet further?
Can you be explicit about the three states of this proposed tri-state pref? Nick _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
