3 ms·
Side question: whatever happened to Chrome blocking autoplay videos like this horrible and incredibly loud one? It's supposed to have been in place for a year
by crazygringo 8y ago
Side question: whatever happened to Chrome blocking autoplay videos like this horrible and incredibly loud one?
It's supposed to have been in place for a year or so... but it's clearly not working. If this particular one isn't blocked, then what ones are?
I'm on up-to-date Chrome 72...
[1] https://developers.google.com/web/updates/2017/09/autoplay-policy-changes https://developers.google.com/web/updates/2017/09/autoplay-p...
- etaioinshrdlu 8y agoThe autoplay blocking involves a complicated set of heuristics involving the domain name and your past behavior with that domain...
- llukas 8y agoor you can just turn it off in new firefox...
- crazygringo 8y agoSo I just checked my heuristics at chrome://media-engagement/ and zdnet.com has a personal MEI of 0.0 with 7 visits (for comparison, YouTube is 0.76), and the stated threshold at the top of that page for allowing video with sound is min 0.2 max 0.3. So just ugh. Disappointed in Chrome that zdnet.com is somehow considered high enough quality to play videos with audio automatically. :(
- skilled 8y agoMan, the first time this happened to me on ZDNet, I literally tweeted out to their Twitter account that they are idiots for putting that pattern in place. It's the loudest autoplay I have ever heard.
- tnorthcutt 8y agozdnet.com has a score of 0 for me, and it still autoplayed.
- dawnerd 8y agozdnet and a few others seem to be doing some tricks to get around it. I right click the tab and mute the site. CNN does the same and it's really freaking annoying.
- danShumway 8y agoChrome has an overall whitelist on top of a user-specific one. I assume that ZDNet overall has a high enough MEI score across all Chrome users that it's allowed until you train the algorithm that you don't want to see it. Additionally, if you navigate within a site (ie, click on another ZDNet article from that same page), that counts as a website interaction, and the new page will be allowed to autoplay. Firefox's upcoming controls are user-controlled instead of based on algorithmic behavior, and they don't have a whitelist. They're available right now, but not turned on by default (yet).