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
Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
Adding dir="rtl" to a <mat-progress-bar> used to flip the direction to right-to-left. This currently doesn't work anymore. The result seems something random:
(note that explicitly setting dir="ltr" does work correctly)
This was already fixed once in 2021, but seems to be broken since then: #22705
…n element
Fixes an issue where the progress bar was looking for `dir="rtl"` only on parent elements, but on itself. We can avoid the problem altogether by using a directionality-agnostic property.
Fixesangular#28572.
…n element
Fixes an issue where the progress bar was looking for `dir="rtl"` only on parent elements, but on itself. We can avoid the problem altogether by using a directionality-agnostic property.
Fixes#28572.
…n element
Fixes an issue where the progress bar was looking for `dir="rtl"` only on parent elements, but on itself. We can avoid the problem altogether by using a directionality-agnostic property.
Fixes#28572.
(cherry picked from commit d0618bc)
Is this a regression?
The previous version in which this bug was not present was
No response
Description
Adding
dir="rtl"
to a<mat-progress-bar>
used to flip the direction to right-to-left. This currently doesn't work anymore. The result seems something random:(note that explicitly setting
dir="ltr"
does work correctly)This was already fixed once in 2021, but seems to be broken since then: #22705
Reproduction
StackBlitz link: https://stackblitz.com/edit/wnrmdf?file=src%2Fexample%2Fprogress-bar-determinate-example.html
Expected Behavior
The progress bar is displayed from right to left.
Actual Behavior
The progress bar is filled in somewhere in the middle, seemingly randomly.
Environment
The text was updated successfully, but these errors were encountered: