Earlier quoted context omitted.
Interesting. Setting this to "Document user activation required" eliminated all autoplay for me.
It seems to work intermittently for me at best. Bloomberg is a notable (notably annoying) example that not only autoplays (though at least without sound) but highjacks your first click on the video (usually trying to pause it) and enables sound instead.
New autoplay policy in Chrome
171–178 of 178 posts
Re: New autoplay policy in Chrome
#172Earlier 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.
Things are so bad now that I keep my earphones plugged in but not in my ear. It's easier than trying to quickly hit mute when I'm surprised by a site and disruptive blaring starts.
And please someone don't say I'm doing it wrong....why can't browser programmers expose a list of tabs playing audio, and allow navigation to each from that list? (And the same goes for tabs consuming excessive CPU - in FF, I can see the offending websites in about:performance, and I can close the tab from there, but what if I wanted to navigate to the tab instead?)
Re: New autoplay policy in Chrome
#173Earlier quoted context omitted.
I think it depends a lot on how stable the learning is. If it converges and becomes harder to unlearn, eventually you'll be working from a stable platform... but it doesn't carry over to another browser unless you use the sign in feature. So you'll get a stable experience within a browser but not between browsers of the same make/model.
> unless you use the sign in feature Which then becomes yet another reason to use the sign in feature, and yet another reason to stay with the same browser brand.
Re: New autoplay policy in Chrome
#174Earlier quoted context omitted.
Right. Of the main browser vendors, Safari and Edge's conflict of interest is they'd prefer people make native apps over webapps. Chrome's conflict of interest is they don't want you to block ads. Firefox is the only browser with user-aligned incentives (as long as they ignore who pays a lot of their income...)
Hmm I guess this analysis explains why IE has sucked for so long
https://www.zdnet.com/article/intel-exec-ms-wanted-to-extend...
> It was in this meeting that Microsoft executives said they intended to "embrace, extend, extinguish" competing technologies, including Internet standard HTML, McGeady said
https://www.justice.gov/sites/default/files/atr/legacy/2006/...
> we will loose [sic] the Internet platform battle if we do not have a significant user installed base. The industry would simply ignore our standards. Few would write Windows apps without the Windows user base. — at your level, if you let your customers deploy Netscape Navigator, you loose [sic] the leadership on the desktop.
Re: New autoplay policy in Chrome
#175Re: New autoplay policy in Chrome
#176Earlier quoted context omitted.
Youtube is the worst, because not only does it autoplay, but for the first 2s or so it's faffing around with JavaScript so no matter what you do in that time it will subsequently start playing. Like, it'll show up as "playing" and you pause it, then leave the tab, and like a second later the video will start despite your having paused it. (for the record, at least half the time I open a youtube video I don't want it…
i'm not sure if this is something on my end or google's, but i've noticed that in the past few weeks whenever I open a youtube video in a new tab (staying in the current tab), it won't play until i switch to the new one.
Re: New autoplay policy in Chrome
#177This broke my accessibility extension for Chrome that lets users control the browser with their voice instead of hands. Since voice isn't counted as a "gesture" the user can't say "play" to start a a video. It's not just autoplay it's any sort of dynamic (js initiated) playing of media.
Re: New autoplay policy in Chrome
#178This broke my accessibility extension for Chrome that lets users control the browser with their voice instead of hands. Since voice isn't counted as a "gesture" the user can't say "play" to start a a video. It's not just autoplay it's any sort of dynamic (js initiated) playing of media.
Hey, would you mind sharing the extension you are using? This should not happen and I would like to help fixing it.
https://chrome.google.com/webstore/detail/lipsurf/lnnmjmalak...
I added an ugly workaround, a slide to the tutorial that asks users to go into their flags and allow autoplay without any gestures. Chrome extensions should have better privileges for playing videos, fullscreening etc. IMO but it all needs to be hacked around limiting extensions.