Skip to content

build: fix not being able to test MDC density in RTL #21398

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

Merged
merged 1 commit into from
Jan 7, 2021

Conversation

crisbeto
Copy link
Member

Our dev app is set up so that the density styles are set on the body while the dir is set only around the content. The problem is that MDC's mixins output density styles for RTL in the format [dir='rtl'] .density .foo which means that the directionality has to be a level above the density class or we won't get an accurate representation of how the components look. This threw me off for a while earlier today, because I noticed that the MDC slide toggle didn't behave correctly in RTL.

These changes fix the issue by moving the dir a level up and applying the density class in a couple of places.

Our dev app is set up so that the density styles are set on the `body` while the `dir` is
set only around the content. The problem is that MDC's mixins output density styles for
RTL in the format `[dir='rtl'] .density .foo` which means that the directionality has to be
a level above the density class or we won't get an accurate representation of how the
components look. This threw me off for a while earlier today, because I noticed that
the MDC slide toggle didn't behave correctly in RTL.

These changes fix the issue by moving the `dir` a level up and applying the density class
in a couple of places.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent merge safe target: patch This PR is targeted for the next patch release labels Dec 19, 2020
@crisbeto crisbeto requested a review from mmalerba as a code owner December 19, 2020 15:06
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Dec 19, 2020
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 the action: merge The PR is ready for merge by the caretaker label Jan 5, 2021
@annieyw annieyw merged commit 69b0a72 into angular:master Jan 7, 2021
annieyw pushed a commit that referenced this pull request Jan 7, 2021
Our dev app is set up so that the density styles are set on the `body` while the `dir` is
set only around the content. The problem is that MDC's mixins output density styles for
RTL in the format `[dir='rtl'] .density .foo` which means that the directionality has to be
a level above the density class or we won't get an accurate representation of how the
components look. This threw me off for a while earlier today, because I noticed that
the MDC slide toggle didn't behave correctly in RTL.

These changes fix the issue by moving the `dir` a level up and applying the density class
in a couple of places.

(cherry picked from commit 69b0a72)
wagnermaciel pushed a commit to wagnermaciel/components that referenced this pull request Jan 14, 2021
Our dev app is set up so that the density styles are set on the `body` while the `dir` is
set only around the content. The problem is that MDC's mixins output density styles for
RTL in the format `[dir='rtl'] .density .foo` which means that the directionality has to be
a level above the density class or we won't get an accurate representation of how the
components look. This threw me off for a while earlier today, because I noticed that
the MDC slide toggle didn't behave correctly in RTL.

These changes fix the issue by moving the `dir` a level up and applying the density class
in a couple of places.
@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 Feb 7, 2021
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 P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants