Skip to content

fix(material/menu): prevent menu styles from leaking to other components #27378

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
Jun 30, 2023

Conversation

crisbeto
Copy link
Member

The menu theme was including the MDC list styles directly at the root of the theme which caused to leak into other components like mat-list.

The mixins will be removed in #27377, however currently the screenshot tests of a lot of internal targets assume that the leaky styles will be there which breaks the presubmit of #27377.

These changes introduce a temporary wrapper class around the mixins so that the incorrect screenshots can be approved before trying to land #27377.

@crisbeto crisbeto added 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 labels Jun 28, 2023
@crisbeto crisbeto force-pushed the menu-leaky-styles branch 2 times, most recently from e77705c to c57238c Compare June 28, 2023 11:14
The menu theme was including the MDC list styles directly at the root of the theme which caused to leak into other components like `mat-list`.

The mixins will be removed in angular#27377, however currently the screenshot tests of a lot of internal targets assume that the leaky styles will be there which breaks the presubmit of angular#27377.

These changes introduce a *temporary* wrapper class around the mixins so that the incorrect screenshots can be approved before trying to land angular#27377.
@crisbeto crisbeto force-pushed the menu-leaky-styles branch from c57238c to a71fffa Compare June 29, 2023 05:13
@crisbeto crisbeto requested a review from andrewseguin June 30, 2023 12:15
@crisbeto crisbeto self-assigned this Jun 30, 2023
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Jun 30, 2023
@crisbeto crisbeto merged commit 06f8544 into angular:main Jun 30, 2023
crisbeto added a commit that referenced this pull request Jun 30, 2023
…nts (#27378)

The menu theme was including the MDC list styles directly at the root of the theme which caused to leak into other components like `mat-list`.

The mixins will be removed in #27377, however currently the screenshot tests of a lot of internal targets assume that the leaky styles will be there which breaks the presubmit of #27377.

These changes introduce a *temporary* wrapper class around the mixins so that the incorrect screenshots can be approved before trying to land #27377.

(cherry picked from commit 06f8544)
crisbeto added a commit to crisbeto/material2 that referenced this pull request Jul 22, 2023
After angular#27377 and angular#27378 we no longer use MDC classes directly in the markup. Instead we either use our own styles or we target our selectors with MDC mixins. However, the MDC classes were left in to reduce the amount of internal breakages. These leftover styles can still cause styles to bleed in from the MDC list so this change removes any remaining references.
crisbeto added a commit to crisbeto/material2 that referenced this pull request Jul 22, 2023
After angular#27377 and angular#27378 we no longer use MDC classes directly in the markup. Instead we either use our own styles or we target our selectors with MDC mixins. However, the MDC classes were left in to reduce the amount of internal breakages. These leftover styles can still cause styles to bleed in from the MDC list so this change removes any remaining references.
crisbeto added a commit that referenced this pull request Jul 22, 2023
After #27377 and #27378 we no longer use MDC classes directly in the markup. Instead we either use our own styles or we target our selectors with MDC mixins. However, the MDC classes were left in to reduce the amount of internal breakages. These leftover styles can still cause styles to bleed in from the MDC list so this change removes any remaining references.

(cherry picked from commit 5a7da12)
crisbeto added a commit that referenced this pull request Jul 22, 2023
After #27377 and #27378 we no longer use MDC classes directly in the markup. Instead we either use our own styles or we target our selectors with MDC mixins. However, the MDC classes were left in to reduce the amount of internal breakages. These leftover styles can still cause styles to bleed in from the MDC list so this change removes any remaining references.
@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 Jul 31, 2023
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 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.

2 participants