Google Chrome yesterday announced its initiative in blocking autoplay web video in Chrome browser. It is a perfect move to stop the most irritating and bandwidth consuming autoplay videos.
Chrome released a roadmap on this, starting from Chrome 63 they are to add a new user option which allows users to completely block audio for a website and it will persist among perusing sessions, permitting users to modify when and where the sound will play.
Starting with Chrome 64, autoplay will be allowed when either the media won’t play sound, or the user has indicated an interest in the media. This will allow autoplay to occur when users want media to play, and respect users’ wishes when they don’t.
With Safari version 11 it enables more granular options enabling users to mute sound or even completely blocking the auto play media.
.png
)
With the Chrome’s new update media content will be allowed to autoplay only under the following conditions:
- The content is muted or does not include any audio (video only)
- The user tapped or clicked somewhere on the site during the browsing session
- On mobile, if the site has been added to the Home Screen by the user
- On desktop, if the user has frequently played media on the site, according to the Media Engagement Index
Roadmap
September 2017 New autoplay policies announced Site muting available in M63 Beta Begin collecting Media Engagement Index (MEI) data in M62 Canary and Dev
October 2017 Site muting available in M63 Stable. Autoplay policies available in M63+ Canary and Dev
December 2017 Autoplay policies available in M64 Beta
January 2018 Autoplay policies available in M64 Stable
With these new options, it will give more control to the users in controlling media and also be making it easier for publishers to implement autoplay where it benefits the user.
