New autoplay policy in Chrome • Hacker News Board

Re: New autoplay policy in Chrome

#131

Post by digi_owl » Mon, May 07, 2018, 9:59 AM UTC

Aardwolf wrote: post #127

rtpg wrote: post #107

Earlier quoted context omitted.

yeah, this seems like such an intense thing to do My bet is that they did this to not break Youtube. I mean it makes sense (you don't want video sites to not work) but it's also such a hacky sort of thing I don't get why they couldn't make this a permission thing like a mic. Ask the website to allow autoplay.

> My bet is that they did this to not break Youtube. Which is fine to me. If I go to a website specifically for videos, I want it to autoplay, having to press play is a pointless action. If I go to a website to read articles, I do not want autoplay, and I definitely don't want the video to even follow me around as a tiny minimized window when I scroll down and yes I will close the tab or press back pretty quick if th…

I may go there to view a video, but that does not mean i want it to start playing the moment the page starts loading.

Re: New autoplay policy in Chrome

#132

Post by barrystaes » Mon, May 07, 2018, 10:06 AM UTC

I'm happy to see that many people here already suggested that this behaviour is NOT PREDICTABLE. In my view thats a must for any device or tool, including software/computers.

Re: New autoplay policy in Chrome

#133

Post by abzolv » Mon, May 07, 2018, 10:09 AM UTC

"In fact, in Chrome a significant number of autoplays are paused, muted, or have their tab closed within six seconds by people who don’t want them."

How would they know that without tracking and centrally recording your autoplay actions in Chrome?

Re: New autoplay policy in Chrome

#134

Post by Aardwolf » Mon, May 07, 2018, 10:10 AM UTC

digi_owl wrote: post #131

Aardwolf wrote: post #127

Earlier quoted context omitted.

> My bet is that they did this to not break Youtube. Which is fine to me. If I go to a website specifically for videos, I want it to autoplay, having to press play is a pointless action. If I go to a website to read articles, I do not want autoplay, and I definitely don't want the video to even follow me around as a tiny minimized window when I scroll down and yes I will close the tab or press back pretty quick if th…

I may go there to view a video, but that does not mean i want it to start playing the moment the page starts loading.

Then the preference differs per person. Optimal for me would be if anyone can create a personal whitelist of websites that may autoplay :)

EDIT: or "learn" I guess, let's see how long it takes to learn my simple whitelist and how often it will randomly decide to change :p

Re: New autoplay policy in Chrome

#135

Post by cdancette » Mon, May 07, 2018, 10:10 AM UTC

digi_owl wrote: post #131

Aardwolf wrote: post #127

Earlier quoted context omitted.

> My bet is that they did this to not break Youtube. Which is fine to me. If I go to a website specifically for videos, I want it to autoplay, having to press play is a pointless action. If I go to a website to read articles, I do not want autoplay, and I definitely don't want the video to even follow me around as a tiny minimized window when I scroll down and yes I will close the tab or press back pretty quick if th…

I may go there to view a video, but that does not mean i want it to start playing the moment the page starts loading.

that's why it's learning from your actions

Re: New autoplay policy in Chrome

#136

Post by mborch » Mon, May 07, 2018, 10:11 AM UTC

abzolv wrote: post #133

"In fact, in Chrome a significant number of autoplays are paused, muted, or have their tab closed within six seconds by people who don’t want them." How would they know that without tracking and centrally recording your autoplay actions in Chrome?

From Google Analytics.

Re: New autoplay policy in Chrome

#137

Post by rtpg » Mon, May 07, 2018, 10:12 AM UTC

Aardwolf wrote: post #127

rtpg wrote: post #107

Earlier quoted context omitted.

yeah, this seems like such an intense thing to do My bet is that they did this to not break Youtube. I mean it makes sense (you don't want video sites to not work) but it's also such a hacky sort of thing I don't get why they couldn't make this a permission thing like a mic. Ask the website to allow autoplay.

> My bet is that they did this to not break Youtube. Which is fine to me. If I go to a website specifically for videos, I want it to autoplay, having to press play is a pointless action. If I go to a website to read articles, I do not want autoplay, and I definitely don't want the video to even follow me around as a tiny minimized window when I scroll down and yes I will close the tab or press back pretty quick if th…

That's the rub. How do you differentiate between the articles thing and the video thing?

Re: New autoplay policy in Chrome

#138

Post by gcb0 » Mon, May 07, 2018, 10:17 AM UTC

koolba wrote: post #51

> As 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. This way, Chrome gives you a personalized, predictable browsing experience. Predictable in a user application is the same result from the same action every time. UX changing based on opaque logic and heuristics is anything but p…

hi, it looks like you are writing a web browser. I can help with it.

(hope kids still remember clippy)

Re: New autoplay policy in Chrome

#139

Post by maskros » Mon, May 07, 2018, 10:21 AM UTC

cdancette wrote: post #135

digi_owl wrote: post #131

Earlier quoted context omitted.

I may go there to view a video, but that does not mean i want it to start playing the moment the page starts loading.

that's why it's learning from your actions

Not the same thing, if going by the article. If I eventually play all the videos, at my own leasure, it will still learn that I play the videos and start playing immediately when the page loads.

Re: New autoplay policy in Chrome

#140

Post by cm2187 » Mon, May 07, 2018, 10:44 AM UTC

rtpg wrote: post #137

Aardwolf wrote: post #127

Earlier quoted context omitted.

> My bet is that they did this to not break Youtube. Which is fine to me. If I go to a website specifically for videos, I want it to autoplay, having to press play is a pointless action. If I go to a website to read articles, I do not want autoplay, and I definitely don't want the video to even follow me around as a tiny minimized window when I scroll down and yes I will close the tab or press back pretty quick if th…

That's the rub. How do you differentiate between the articles thing and the video thing?

You get a convenient way to enable auto play on that website only.