Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New autoplay policy in Chrome

blog.google

Post reply on HN
Print view View original

141–150 of 178 posts

Re: New autoplay policy in Chrome

#141

Post by Jaruzel »

potench wrote: post #98

Preroll (IMA3) integration with an HTML5 video player is a really tricky dance when you’re trying to support mobile/desktop browsers with a resilient and consistent video player experience. Autoplay has been one of the most difficult differences to manage across browsers. There’s no browser api that tells you if autoplay is supported, and you won’t get meaningful errors when you try to autoplay when you can’t. Ultima…

> Ultimately the right solution is to just-don’t-autoplay-ever, but it’s a hard sell when you see a 20-40% drop in VOD begins when you remove autoplay.

Which tells me that with autoplay enabled, 20-40% of people are probably clicking 'stop' just after the video starts playing, so aren't watching your content anyway.

Re: New autoplay policy in Chrome

#143

Post by nukeop »

This is yet another attempt by Google to leverage their browser market hegemony against other publishers. Who wants to bet that Youtube will have autoplay enabled by default in all cases, while other ad providers will have theirs disabled?

Re: New autoplay policy in Chrome

#144

Post by tim333 »

rtpg wrote: post #107
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…

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.

Killing autoplay wouldn't break Youtube for me. I love Youtube and mostly hate autoplay. What's so bad about clicking a play button?

Re: New autoplay policy in Chrome

#145

Post by ebbv »

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…

100%. And it’s like they have forgotten anybody ever shares computers in a family. Google has lost the plot lately.

Re: New autoplay policy in Chrome

#146

Post by Macha »

pryce wrote: post #118
arijun wrote: post #114

Earlier quoted context omitted.

"Allow this website to automatically play videos in the future" sounds exactly like autoplay to me. Just not the first time.

I have developed an instinctual reaction to automatically deny permissions like remotely that for any website, and I think most people have. Websites asking for permission to send notifications provokes the same irritation. I think - "I am in the middle of doing something, I don't want to stop and think carefully about permissions for some vague and abstract future encounters, I want the annoying dialog to go away an…

The only websites where I have allowed notifications are discord and slack. I can't see any reason why a news site should be allowed notifications. I know why the site wants to send me notifications - alert on new articles loaded, draw me back in, keep my traffic, just like why they want me to install a native app - but I can't see the benefit to me.

Still, if I've managed to allow notifications to slack/discord I'm sure I could figure out allowing autoplay on YouTube/twitch.

Re: New autoplay policy in Chrome

#147

Post by Macha »

ripdog wrote: post #124
zaarn wrote: post #104

Earlier quoted context omitted.

I don't want YouTube to autoplay, most of the time, I'm opening a lot of YT tabs at once and sometimes I need to seek out a specific one I am interested in most. It would be much nicer if the various plugins I use to control that behaviour wouldn't stop working every 4 months due to another youtube redesign (whether in UI or Backend on the Client).

Firefox does this by default. Background tabs do not autoplay, but the foreground tab does.

Huh, I thought this was a behaviour YouTube/twitch did manually as it doesn't seem 100% reliable on news sites.

Re: New autoplay policy in Chrome

#148

Post by dwighttk »

always_good wrote: post #54
sanxiyn wrote: post #18

> Chrome does this by learning your preferences... This way, Chrome gives you a personalized, predictable browsing experience. In my experience, "learning" and "predictable" do not go together.

Reminds me of fuzzy matching systems like Alfred that will try to learn which key combos you use to launch each app instead of trying to offer you predictability. But "fi " never launches Firefox anymore because of that one time you accidentally launched Finder instead. And since you keep accidentally launching Finder that way, it never learns that you want Firefox. So you try "f " but you accidentally launch Flux. A…

For a while “c” was calendar, “ca” was calculator, “cal” was calendar again. I use launch bar and that has been my only irritation. It seems to continue learning and not get stuck on certain key combos.

Re: New autoplay policy in Chrome

#150

Post by mariusmg »

cm2187 wrote: post #140
rtpg wrote: post #137

Earlier quoted context omitted.

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.

That would mean everyone will have to "whitelist" Youtube and allow playback after updating Chrome. No way this "option" gets the stamp of approval from Google management.
Post reply on HN