Skip to content

fix(material/chips): increase specificity of chip ripple selector #27457

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
Jul 17, 2023

Conversation

wagnermaciel
Copy link
Contributor

  • avoids issues where chip ripple styles are overriden by mat-ripple styles

* avoids issues where chip ripple styles
  are overriden by mat-ripple styles
@wagnermaciel wagnermaciel added target: patch This PR is targeted for the next patch release action: merge The PR is ready for merge by the caretaker labels Jul 17, 2023
@wagnermaciel wagnermaciel merged commit 8b06180 into angular:main Jul 17, 2023
wagnermaciel added a commit that referenced this pull request Jul 17, 2023
…7457)

* avoids issues where chip ripple styles
  are overriden by mat-ripple styles

(cherry picked from commit 8b06180)
AnthonyFr75 pushed a commit to AnthonyFr75/components that referenced this pull request Jul 31, 2023
…gular#27457)

* avoids issues where chip ripple styles
  are overriden by mat-ripple styles
stephenrca pushed a commit to stephenrca/components that referenced this pull request Aug 2, 2023
…gular#27457)

* avoids issues where chip ripple styles
  are overriden by mat-ripple styles
@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 Aug 17, 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 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