Skip to content

fix(material-experimental/mdc-select): panel losing max-height if menu is opened after select #21341

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
Dec 17, 2020

Conversation

crisbeto
Copy link
Member

If an MDC-based mat-menu is opened after a mat-select, the select will lose its max-height, because its selector specificity is too low and it gets overwritten by the menu which uses the same set of mixins.

These changes resolve the issue by increasing the specificity.

…u is opened after select

If an MDC-based `mat-menu` is opened after a `mat-select`, the select will lose
its `max-height`, because its selector specificity is too low and it gets overwritten
by the menu which uses the same set of mixins.

These changes resolve the issue by increasing the specificity.
@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 Dec 13, 2020
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Dec 13, 2020
@annieyw annieyw added the action: merge The PR is ready for merge by the caretaker label Dec 14, 2020
@mmalerba mmalerba merged commit c530067 into angular:master Dec 17, 2020
mmalerba pushed a commit that referenced this pull request Dec 17, 2020
…u is opened after select (#21341)

If an MDC-based `mat-menu` is opened after a `mat-select`, the select will lose
its `max-height`, because its selector specificity is too low and it gets overwritten
by the menu which uses the same set of mixins.

These changes resolve the issue by increasing the specificity.

(cherry picked from commit c530067)
crisbeto added a commit to crisbeto/material2 that referenced this pull request Dec 18, 2020
…if menu is opened after autocomplete

Along the same lines as angular#21341. If an MDC-based mat-menu is opened after a
mat-autocomplete, the autocomplete will lose its max-height, because its
selector specificity is too low and it gets overwritten by the menu which uses
the same set of mixins.

These changes resolve the issue by increasing the specificity.
annieyw pushed a commit that referenced this pull request Jan 6, 2021
…if menu is opened after autocomplete (#21394)

Along the same lines as #21341. If an MDC-based mat-menu is opened after a
mat-autocomplete, the autocomplete will lose its max-height, because its
selector specificity is too low and it gets overwritten by the menu which uses
the same set of mixins.

These changes resolve the issue by increasing the specificity.
annieyw pushed a commit that referenced this pull request Jan 6, 2021
…if menu is opened after autocomplete (#21394)

Along the same lines as #21341. If an MDC-based mat-menu is opened after a
mat-autocomplete, the autocomplete will lose its max-height, because its
selector specificity is too low and it gets overwritten by the menu which uses
the same set of mixins.

These changes resolve the issue by increasing the specificity.

(cherry picked from commit 3335a92)
wagnermaciel pushed a commit to wagnermaciel/components that referenced this pull request Jan 14, 2021
…u is opened after select (angular#21341)

If an MDC-based `mat-menu` is opened after a `mat-select`, the select will lose
its `max-height`, because its selector specificity is too low and it gets overwritten
by the menu which uses the same set of mixins.

These changes resolve the issue by increasing the specificity.
wagnermaciel pushed a commit to wagnermaciel/components that referenced this pull request Jan 14, 2021
…if menu is opened after autocomplete (angular#21394)

Along the same lines as angular#21341. If an MDC-based mat-menu is opened after a
mat-autocomplete, the autocomplete will lose its max-height, because its
selector specificity is too low and it gets overwritten by the menu which uses
the same set of mixins.

These changes resolve the issue by increasing the specificity.
@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 Jan 17, 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