We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Bug
Setting a chips color property to 'Primary', 'Accent' or 'Warn' changes the chip color based on the active theme.
Setting a chips color property to 'Primary', 'Accent' or 'Warn' does not change the chip color.
Set the color property on a chip and observe no change. A demo of this can be view in the Component Examples: https://material.angular.io/components/chips/examples
The desired behaviour is what is described by the docs.
Tested using what ever version is active on the Material website on Chrome Version 60.0.3112.113 (Official Build) (64-bit)
The text was updated successfully, but these errors were encountered:
See #7261
Sorry, something went wrong.
Closing as fixed by #7285
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.
No branches or pull requests
Bug, feature request, or proposal:
Bug
What is the expected behavior?
Setting a chips color property to 'Primary', 'Accent' or 'Warn' changes the chip color based on the active theme.
What is the current behavior?
Setting a chips color property to 'Primary', 'Accent' or 'Warn' does not change the chip color.
What are the steps to reproduce?
Set the color property on a chip and observe no change.
A demo of this can be view in the Component Examples: https://material.angular.io/components/chips/examples
What is the use-case or motivation for changing an existing behavior?
The desired behaviour is what is described by the docs.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Tested using what ever version is active on the Material website on Chrome Version 60.0.3112.113 (Official Build) (64-bit)
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: