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(material-experimental/mdc-chips): use ripple target for state interactions #17681

Merged
merged 1 commit into from
Nov 26, 2019

Conversation

andrewseguin
Copy link
Contributor

Similar to what we did with button, checkbox. Use MDC's ripple target container for state interactions (focus, hover, active) rather than trying to do our own. This reduces our amount of overrides, aligns us better with their styles, fixes some bugs (e.g. the state color should match the text color, right now its always black), and helps us get it into using GM styles

@andrewseguin andrewseguin added the target: patch This PR is targeted for the next patch release label Nov 12, 2019
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 12, 2019
@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Nov 12, 2019
@jelbourn jelbourn merged commit 7aa522a into angular:master Nov 26, 2019
@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 Dec 27, 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 target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants