context menu actions don't work when animations are disabled

[magiruuvelvet]

I encountered an annoying issue. While I think this warrants a bug report I don't know any specifics yet. I just want to make this issue visible.

The context menu (play, add to playlist, download, copy stream URL, media info) is effectively useless when animations are disabled because their respective actions seem to only trigger on animationend events, which in itself is silly enough. Business logic should not be coupled with animation timers, as animations are purely cosmetic.

I cross-checked by temporarily enabling animations, and the context menu actions triggered properly, so they are indeed coupled with animation timers/events.

Is this by design or an oversight? I very rarely stumble across issues like this, as most websites and services work just fine with animations disabled.

[thornbill]

How did you disable animations?

[magiruuvelvet]

with globally injected (manifest v2 extension) CSS and JavaScript. forcing several animation and transition related properties to 0 by using tricks to gain the highest CSS specificity that even overwrites important inline styles. the JavaScript code stubs some (not all yet) web animation APIs so that animation callbacks resolve immediately instead of having to wait for the animation to complete.

i'm still fighting with animationend event listeners not triggering. i only encountered 2 services that break so far. one of them being the Jellyfin web interface. i use the CSS since almost a year now, the JS is relatively new.

my CSS and JS solve personal issues for me, as the modern web tends to ignore prefers-reduced-motion and likes to over-animate everything, wasting my time and making me physically ill.

EDIT: before it gets forgotten. i think coupling non-animation logic (like copying a link to the clipboard after i press a button) with animation timers/events is bad engineering. i never do this myself and i see no reason why it should be implemented like this. animations are purely cosmetic afterall.

[magiruuvelvet]

i have good news. i revisited my browser extension and improved it since the last iteration. the context menu actions now trigger when i click on them; and they trigger immediately (somewhere in the ~0.0n millisecond range) - no useless waiting for animations to complete.

i decided to publish the source code, as this version will hopefully cause the least breakage. https://github.com/magiruuvelvet/mv2-kill-animations