New autoplay policy in Chrome

#1

Post by AndersSandvik » Sun, May 06, 2018, 9:00 PM UTC

New autoplay policy in Chrome
blog.google

Re: New autoplay policy in Chrome

#2

Post by gcb0 » Sun, May 06, 2018, 9:38 PM UTC

summary: google allow 800 of the international youtube domains to autoplay, plus some 200 other publishers to pretend they are neutral.

Re: New autoplay policy in Chrome

#3

Post by fwdpropaganda » Sun, May 06, 2018, 9:45 PM UTC

gcb0 wrote: post #2

summary: google allow 800 of the international youtube domains to autoplay, plus some 200 other publishers to pretend they are neutral.

I guess after that €2bn EU fine on the Google Shopping case they've learned to start pretending to be neutral before the fines.

Re: New autoplay policy in Chrome

#4

Post by slow_donkey » Sun, May 06, 2018, 10:05 PM UTC

gcb0 wrote: post #2

summary: google allow 800 of the international youtube domains to autoplay, plus some 200 other publishers to pretend they are neutral.

Can you provide proof, this is completely unsubstantiated purely from the blog

Re: New autoplay policy in Chrome

#5

Post by Jyaif » Sun, May 06, 2018, 10:07 PM UTC

accurate summary: If you don’t have browsing history, Chrome allows autoplay for over 1,000 sites where we see that the highest percentage of visitors play media with sound. As you browse the web, that list changes as Chrome learns.

Re: New autoplay policy in Chrome

#6

Post by kbenson » Sun, May 06, 2018, 10:07 PM UTC

gcb0 wrote: post #2

summary: google allow 800 of the international youtube domains to autoplay, plus some 200 other publishers to pretend they are neutral.

> summary: google allow 800 of the international youtube domains to autoplay, plus some 200 other publishers to pretend they are neutral.

What? How is that an accurate summary? The whole post is about how Chrome will learn your preference for whether to autoplay on domains, not about how it is whitelisting certain domains.

Re: New autoplay policy in Chrome

#7

Post by benbro » Sun, May 06, 2018, 10:08 PM UTC

I couldn't find a way to detect autoplay failure when using the YouTube iframe API. We can catch promise failure when using a normal video element. https://developers.google.com/web/updates/2017/09/autoplay-p...

Re: New autoplay policy in Chrome

#8

Post by curt15 » Sun, May 06, 2018, 10:08 PM UTC

>s you browse the web, that list changes as Chrome learns and enables autoplay on sites where you play media with sound during most of your visits, and disables it on sites where you don’t.

What about disabling autoplay even without sound? Unwanted autoplay videos burn through battery even while muted.

Re: New autoplay policy in Chrome

#9

Post by Amelorate » Sun, May 06, 2018, 10:10 PM UTC

gcb0 wrote: post #2

summary: google allow 800 of the international youtube domains to autoplay, plus some 200 other publishers to pretend they are neutral.

My interpretation of the article was that chrome ships with a blocklist of websites that have annoying autoplay features, but will automatically remove websites from that blocklist that you usually start by playing their videos, and automatically adds websites to the blocklist if the first thing you do is pause the video.

Youtube probably is not on the blocklist, but it will add youtube to your personal blocklist if you always pause the videos.

Re: New autoplay policy in Chrome

#10

Post by crystaln » Sun, May 06, 2018, 10:29 PM UTC

The best way to improve autoplay is to disable it.

chrome://flags/#autoplay-policy