add: new default plugin that fixes ui lag by disabling animations for reduced motion instead of using near-zero durations#10
Merged
RoxyBoxxy merged 1 commit intoRoxyBoxxy:mainfrom Mar 21, 2026
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fluxer's reduced motion css rule uses
animation-duration: 0.01msandtransition-duration: 0.01mson every element via the*selector, this doesn't actually skip animations... the browser still schedules the full transition lifecycle (fires transitionstart/transitionend events, triggers reflows and repaints) but tries to complete it in a timeframe shorter than a single frame and this causes noticeable lag when clicking around the app (switching channels, opening settings, etc...) because every interaction triggers hundreds of micro-transitions across the entire dom treethe counterintuitive symptom is that turning animations on actually removes the lag, because it removes this universal override and lets each element use its own normal gpu-composited transitions
since their PRs are disabled for now, this adds a default betterfluxer plugin that injects a corrected css rule using
animation: none !importantandtransition: none !important, which tells the browser to completely skip the animation/transition subsystem entirely and also extends the selector to cover::beforeand::afterpseudo-elements which were previously unaffected