I think it would be better to just disable autoplay on all websites, and then let me manually enable it. I pretty much continue to install Adblock so I can kill the auto-play elements on websites that just should not autoplay.
100% agree.
New autoplay policy in Chrome
151–160 of 178 posts
Re: New autoplay policy in Chrome
#152If the heuristics are a good as the Android direct-share menu (which suggest contacts I've never talked to..), I'm not very confident it will be a success.
Re: New autoplay policy in Chrome
#153> 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.
>I don't get why they couldn't make this a permission thing like a mic. Ask the website to allow autoplay.
Allow location access? Y/N
Allow autoplay? Y/N
Safe this password? Y/N
Translate website? Y/N
This website uses cookies. OK
Do you want our newsletter? NO
Yeah, I don't know either. Adding to that list sounds like a great idea.
Re: New autoplay policy in Chrome
#154Earlier 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's exactly what they did, but they pre-populated the whitelist with 1000 entries of video streaming sites. If you want to add your own, simply press play in the respective site.
Re: New autoplay policy in Chrome
#155I think the real rub here is that the developer of the website doesn’t know if Autoplay is going to work or not. From what i read on this the site doesn’t not get access to any information on if Autoplay did work or is going to work. For many business type of applications this is critical as being as low friction as possible is very important. Autoplay for a web conference, for example, makes perfect sense. But the JavaScript developer doesn’t know if this event failed or worked. Plus what if you aren’t in active development on your product that relies on this? You have to go modify functionality that has been perfectly fine for years.
I also don’t like how quick google is to make such unilateral changes and just boom there they are in production on the web. Good luck Keeping your site browser agnostic. The but ticket for this feature even advised that site developers check to see if the browser is chrome first and then do different logic. What a mess.
Re: New autoplay policy in Chrome
#156I wish we could just code up a permission prompt like you have for microphone and geo access.
Re: New autoplay policy in Chrome
#157Preroll (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.
You’d need to track your minutes watched per video to see if there’s a drop. I threw an in-exact percentage out as an example, but from what I recall on my last project with video, minutes watched per video went up, not down. Autopilot features work better than you would think...
Re: New autoplay policy in Chrome
#158Earlier quoted context omitted.
Do we really have to pander to people who can’t find a play button? How do these people function at crosswalks or in elevators?
Well, crosswalks shouldn't have buttons. Pedestrians shouldn't have the burden of pressing the button in time to cross on the current signal.
That probably works for crosswalks at intersections, but there are other crosswalks with lights. I found a really nice one that turns the lights yellow as soon as you push the button.
Re: New autoplay policy in Chrome
#159Bret Victor's response: https://twitter.com/worrydream/status/993167096992288771
I genuinely do not understand the artist in the replies who says this has destroyed their work. Can't the website require you to click/tap once to start its thing, without negative impact? I feel like I must be missing something. (There's a mention about not updating code for existing work, which might be it?)
Chrome should have some UI that shows that the tab is muted, and they should have a control somewhere so the user can un-mute the page. Currently when I go to one of those pages, there's no way for me to unmute the page at all.
Re: New autoplay policy in Chrome
#160> 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.
In Chrome I can type Ctrl+L You to search YouTube. Chrome figured this out on its own by learning that when I type "You" I usually mean "YouTube". Ever since then that behavior has been very predictable for me. Why would Chrome learning what sites I usually play video on be any different?