Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(progress-bar): query mode not reversing direction in rtl #6922

Merged
merged 1 commit into from
Sep 12, 2017

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Sep 7, 2017

Fixes the progressbar in query mode not reversing its direction in RTL.

Fixes the progressbar in query mode not reversing its direction in RTL.
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 7, 2017
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Sep 7, 2017
@mmalerba mmalerba merged commit 8a21881 into angular:master Sep 12, 2017
josephperrott pushed a commit to josephperrott/components that referenced this pull request Sep 15, 2017
…#6922)

Fixes the progressbar in query mode not reversing its direction in RTL.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants