This seems to be the right way to go... Chrome's current approach[0] is all heuristic and no user input. I think a quick "Allow" with an optional "Remember Me" would be both easier to implement and less confusing than what they have (also not a huge pain for web developers.)

[0]: https://developers.google.com/web/updates/2017/09/autoplay-p...

Google's ongoing approach is to remove the human from the loop. And more and more human facing projects seems to follow suit.

"Any sort of animation"? =(

That would make most good UIs unusable. UI animation and audio aren't remotely the same category of interruption.

Maybe they aren't the same category but there is an indirect link (for me) in that they are both often superfluous and have negative effects on my subjective experience (eg audio: annoyance/data usage, animation: annoyance/slowdown).

I enjoy animation, in art and film. I don't want it in my UIs and always turn it off completely when I have the option. I hated it when Photoshop introduced animated zoom, inertia panning etc, but thankfully could turn those off. It's like a surgeons scalpel with a springy handle, it adds a level of abstraction and indirectness that I don't enjoy. I also prefer to use a Bic Orange razor rather than an over-engineered, sprung, 5-bladed one, because I get direct rather than fuzzy feedback.

The animations in MacOS are honestly a large reason why I don't like it and only use it when I have to. One of the arguments that is often used to justify UI animation is that it helps relate one component to another. Ok so if for some reason I'm unable to work out that the icon I just clicked in the dock caused the application it represents to open, maybe seeing the animation would help. Once. Then I know, so why do I need to see it tens of thousands of times after that, forever re-educating me on this complex relationship of interface components. When I click a button, I just want it to do its job. Not do a little dance for me first. I'm trying to get stuff done.

One of the first things I do with any new Android phone or ROM (after enabling Developer Options) is to turn off all interface animations.

Any of us who have worked with designers or worked as designers ourselves (me, both - and I've made the egotistical mistake I am calling others out for, sure) know that far too often, animations are made because some people think they look 'cool'. Then they come up with back-justifications for them.

I may not be representative of the majority but "That would make most good UIs unusable" couldn't be less true for me.

Yours isn’t a popular opinion in the UI world but I agree with you fully and there are a handful of interaction designers who question the dogma on animations.

I think animations is one of the places where a smart smartphone company could attack Apple on a UI basis...

Apple is wedded to a rich multimedia UI. It’s so tightly connected to their brand they have no voice.

But someone who came in with a low-media, animationless UI could best Apple on speed, General “UI mess”, and energy consumption. An interesting UI brand could be built around that.

I think most of the animations in MacOS are informative and there aren’t many I can think of that are needlessly lengthy or intrusive.

The bouncing application icon lets you know the know your app’s status as it opens, and it doesn’t delay your access to a program. The window spread shows you exactly where each window will be placed so that you can quickly find the one you want, and so on.

What animations aren’t you a fan of?

You can disable animations in macOS and iOS too though, and that also sets the prefers-reduced-motion media query to true in Safari. Bootstrap has just added support for that, but it’s simple to add the same to any web app you’re building (typically you’d use a CSS variable for your default animation speed, and set it to 0 inside the media query).

A whitelist assumes you'll always want all media on a domain to autoplay all the time, which is very likely not the case. I have autoplay disabled in Firefox, even animated gifs have to be started manually, which is exactly what I want, it's the only way to completely avoid surprises. I've heard this is not currently possible in Chrome which seems crazy to me.

Sound is already a permission: chrome://settings/content/sound

Video is, oddly enough, not, even though "images" are.

"Any sort of animation" seems kinda tough to implement without completely breaking just about every modern site. Enforcing it would require, at the very least, disabling JavaScript and crippling CSS.

When I click the upvote button in Hacker News, and the upvote button disappears, would that be considered an animation?

No because there is nothing like -WebKit-transition on it.

Then people would go back to doing their animations with JS at the cost of more CPU usage, worse frame rate and worse battery life.

Finding out whether JS is currently animating an element is about as hard as solving the halting problem.

JS timers and element modifications could be rate limited. Far far far cry from the halting problem.

I don't think so. Definitely a state transition though.

If on click it went grey then disappeared it miiight be considered animated.