Based on a user’s MEI, we believe we can understand whether a user expects audio from a particular website or not – and anticipate the user's intent in the future.
MEI keeps track of how many visits to a site include audio playback that is more than 7 seconds long. We call this index the Media Engagement Index (MEI) and you can view it via chrome://media-engagement. We do this with an index that is stored locally per Chrome profile on a device – it is not synced across devices and is only shared as part of the anonymized user statistics. We detect when users regularly let audio play for more than 7 seconds during most of their visits to a website, and enable autoplay for that website. Read our earlier blog post on the autoplay policy for more detailed examples.Īdditionally, we added a heuristic to learn from users’ past behavior with regard to websites that autoplay audio. However, if the user arrives on a page with autoplay content and they navigated to that page from a page of the same origin, then that content will never be blocked.
#Chrome autoplay video with sound code
Specifically, developers must add code which resumes their content if the user interacts with the webpage. In most cases, the playback will be resumed but in others, a small adjustment to the code will be needed. For websites which expected to be able to autoplay their content, this change will prevent playback by default. # What does the policy change do exactly?Īutoplay is the name given to a piece of content which immediately plays upon the loading of a webpage. This policy change is now scheduled to roll out with Chrome 71 in December 2018. We’ve also made some changes to the implementation of the policy for Web Audio which will reduce the number of websites that need to adjust their code – especially web games – and therefore provide a better experience for our users.
#Chrome autoplay video with sound update
The policy change was released with Chrome 66 Stable in May 2018.Īfter feedback from the Web Audio development community we delayed the release of the Web Audio portion of the autoplay policy to give developers more time to update their websites. In September 2017 we announced an upcoming change to how audio would be handled with autoplay behavior policy in Chrome.
0 kommentar(er)
