New assistant doesn't respect `prefers-reduced-motion`

magiruuvelvet

The new assistant interface has hardcoded JavaScript animations that can't be disabled when forcing the animation and transition CSS properties to 0. This irritates me. Also the animations are too slow for me and waste my time. Please either respect the prefers-reduced-motion setting or use standard CSS animations, so they can be disabled by user-injected CSS.

magiruuvelvet

Thank you for looking into this. Is this perhaps already deployed or still pending? Just asking because there are still animations.
I found out by now how these JavaScript animations are implemented. I'm now injecting custom JavaScript to stub Element.prototype.animate with a no-op implementation. I was successfully able to get rid of most annoying animations that way. The tab switching in the model picker reacts a bit weird in rare cases - probably due to how the internal timer is 0 and events are fired immediately - but generally there are no more animations and switching the tab is instant (0ms).

https://gist.github.com/magiruuvelvet/973540cf0d2419c804a0ef5228c9f039

I hope this will get looked into more seriously. Animations are purely cosmetic and should not be coupled with business logic. Technically the call to Element.prototype.animate should be gated to respect the prefers-reduced-motion flag.