The autoplay policy will also become part of Firefox for Android, and therefore replace its existing one. This will block any non muted autoplay content by default for all websites where user interaction was not detected before. The stable version is expected to be released on March 19th.
On February 4th, Mozilla announced their updated autoplay policy for all users, as part of Firefox 66 beta release.
Let’s take a look at the autoplay horizon now. Quick Tip: In case you are wondering what data is tracked by Google’s MEI, you can view this data by opening this URL in your Chrome browser: chrome://media-engagement/ Fast Forward to Today It only allowed users to disable or enable autoplay globally, not per-site.
Firefox 59 had already implemented autoplay policy, which could be enabled via a flag but it wasn’t obvious to every user. Their policy allowed users to decide for themselves if they wanted to allow autoplay or not by default, globally or per-site. MS Edge (Edge HTML 18) followed shortly and implemented their own autoplay control behavior. However, a user could whitelist websites to allow autoplay and define a general rule for all websites in the “Preferences” section. That’s all that is known about the behaviour of this engine. In September 2018, Apple followed suit and introduced Autoplay policies in Safari 11.0 along with its “automatic interference engine” that blocked autoplay by default for most websites. To do that, it takes into account if a user is visiting this site frequently, how long a user consumes its content, and some other website traffic factors. MEI collected anonymous user data to derive a score for a website to determine if audible autoplay is allowed or not. Google started to roll out their new autoplay policy in April 2018 with Chrome 66, along with its MEI (Media Engagement Index). Let’s have a quick look at what happened last year, here’s our original post for more details: While it was rolled out with the right intentions to help users enjoy their journey through the web, without being “annoyed” by loud, auto-playing audio/video content, it certainly sent website owners and video developers scrambling to make last minute changes to adopt autoplay rules to continue providing a smooth playback experience for their users. Restrictive autoplay policies in browsers were definitely one of the most disruptive changes that took place in 2018.
0 kommentar(er)
