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
Currently the behavior for progress components in fluentui when reduced-motion is active is to have the animation execute 3 times then stop, and have a label prop with Loading... or some indication of buffering. There are a few scenarios that this approach would not be feasible.
For example, using the determinateProgress. When progression towards a 100% completion is required, stopping the bar animation is counterintuitive to the usage of Progress.
This issue is to track research being done to come up with a strategy for how progress components should behave when reduced-motion is active
The text was updated successfully, but these errors were encountered:
Currently the behavior for progress components in fluentui when
reduced-motion
is active is to have the animation execute 3 times then stop, and have alabel
prop withLoading...
or some indication of buffering. There are a few scenarios that this approach would not be feasible.For example, using the
determinate
Progress
. When progression towards a 100% completion is required, stopping the bar animation is counterintuitive to the usage ofProgress
.This issue is to track research being done to come up with a strategy for how progress components should behave when
reduced-motion
is activeThe text was updated successfully, but these errors were encountered: