You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The README mentions that the disableForReducedMotion option is disabled by default.
Why?
I don't understand why you would ever override the accessibility preferences a user has set in their own browser.
In my opinion, the disableForReducedMotion option should not even exist. If the user has indicated that they prefer reduced motion, simply don't run the script at all.
The text was updated successfully, but these errors were encountered:
I discussed this in #114 already. The tl;dr is that I don't know how this library is used, but I do for a fact know that it is not always purely decorative. All my research on this issue strongly stresses the importance of careful consideration on how to replace motion effects -- not always simply remove them -- on a case-by-case basis.
Also, side note, this is a weirdly aggressive stance to take with the developer of a library instead of the developer using a library. Keep in mind, this library does only one single thing: confetti. No one who is using this library is left with the impression that confetti won't happen. No one is being tricked. All developers using this library are doing so on purpose.
The README mentions that the
disableForReducedMotion
option is disabled by default.Why?
I don't understand why you would ever override the accessibility preferences a user has set in their own browser.
In my opinion, the
disableForReducedMotion
option should not even exist. If the user has indicated that they prefer reduced motion, simply don't run the script at all.The text was updated successfully, but these errors were encountered: