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
Is your feature request related to a problem? Please describe.
There is currently a great implementation of default and overridable reducedMotion behavior in MotionConfig and motion components. However, there are no similar parameters in useAnimate controls.
In building the reduced motion accessibility for my client, I have been unable to add certain interactivity due to Framer Motion's built in reducedMotion restrictions. We would greatly appreciate the ability to override these default settings in our components that require useAnimate.
Describe the solution you'd like
I would like the same reducedMotion props available in motion components available to useAnimate control instances.
Describe alternatives you've considered
I have tried to wrap the scope of a useAnimate instance in a MotionConfig but that does not work. I had a brief conversation about this with you on x.com.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
There is currently a great implementation of default and overridable
reducedMotion
behavior inMotionConfig
andmotion
components. However, there are no similar parameters inuseAnimate
controls.In building the reduced motion accessibility for my client, I have been unable to add certain interactivity due to Framer Motion's built in
reducedMotion
restrictions. We would greatly appreciate the ability to override these default settings in our components that requireuseAnimate
.Describe the solution you'd like
I would like the same
reducedMotion
props available inmotion
components available touseAnimate
control instances.Describe alternatives you've considered
I have tried to wrap the
scope
of auseAnimate
instance in aMotionConfig
but that does not work. I had a brief conversation about this with you on x.com.The text was updated successfully, but these errors were encountered: