Same here. However for me it's not only an annoyance, but since I'm on a metered connection (LTE with severe throttling after 50 GB only avoidable by buying extra volume), this is costing me real money. Opening a Bloomberg article in the background will happily autplay a series of videos I may not notice. And that's with uBlock Origin installed.
I just opened such an article and in the 5 minute window since I did so, the page consumed a cool 100 MB for a 2:20 video. It obviously gets worse with longer videos.
I tried it again recently. The mobile app is just too slow to start, and I'm currently stuck with a phone with too little memory to not autokill stuff. I realize Chrome's apparent snappiness is probably due to some questionable and likely anti-competitive integrations by Google, like Microsoft in the 2000s.
+1 It's trivially easy to stop ALL media from autoplaying - including gifs! It's wonderful (but sometimes jarring when I expect a gif to be playing already)
However, it does not seem to work in most cases that I've found. I was super excited when it arrived, but I'm still hunting down the domains of auto-play videos and adding them to a blacklist manually.
The choices seem to be "document user gesture", "user gesture is required", "no user gesture is required", and "default". There needs to be a "never autoplay any media"
They have a reasonably coherent generalization planned for this[0].
Chrome will track a user's actual video consumption habits per origin, and compare it to the user's total visits to that origin. Video consumption is judged to be intentional if play is longer than 7 seconds, audio is unmuted, the tab is active, and the video is bigger than 200x140 px.
Then, if the ratio of actual video consumption to visits is high enough, Chrome desktop will allow autoplay. (My read is that Chrome mobile will wholly disable autoplay.)
If you always pause / mute playback on news sites but let Youtube autoplay, Chrome will learn to allow Youtube to autoplay.
If you always pause/mute playback on Youtube, Chrome will learn not to autoplay Youtube.
You can see what inferences Chrome has made at chrome://media-engagement .
(I'm not a Google employee nor a Chrome developer and may be accidentally misrepresenting this policy, but I've attempted to describe it accurately.)
Off-by-default is an option now for advanced users (such as might be reading HN). On the same page I linked in my earlier comment you are responding to, see:
> You can try out these new policies by setting the experimental flag chrome://flags/#autoplay-policy to "Document user activation is required." in Chrome 64.
Like you, that is my preference as well, and I have set the flag.
Are those AND conditions or OR conditions on autoplays? If and, will we see these videos shrink to 199x139 to avoid tripping the detectors? Oh happy day, the pause button will be even smaller and harder to click!
I think you misunderstand the metric. Videos smaller than 199x139 will not qualify as "user intended to watch this video" and therefore Chrome will disable autoplay on those sites.
I'm sure the metrics say it boosts engagement or they wouldn't do it, but to me it renders their UX unusable -- I can't read a description because the video is blaring at me.
I suspect the UX will be that once audio is enabled for any video in the page any subsequent videos will get a free pass, and not some special treatment for Google.
Yeah, I doubt they're white-listing their domains, my point is just they are (arguably) the worst offenders of auto-playing videos, so I take this announcement with a grain of salt.
That option is to automatically switch to a new video after completing the current video. The link is about videos that start playing when you open a link- in YouTube's case, the first video in the queue.
Higher priority should be to mute websites that don't have media content.
Two ideas: Either make it permission based like location, or have a master volume setting for sounds like rely on javascript (excluding html5, flash, etc.). I'm not 100% sure about the details for the latter, but that'd be very convenient.
I'm almost always caught off guard when a customer service widget pops up on the bottom right corner of the screen with an annoying bell sound.
Doesn't scale. Firefox is already introducing option to block "notification permission" requests as all sites spam with it, even when it makes little to none sense.