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
That colors exactly match the color palettes on material.io guidelines.
Sass palette $mat-green's 500 hue, has a white contrast color instead of the guideline's black color
$green : mat-palette($mat-green); $contrast: mat-contrast($mat-green, 500); //which is default
It doesn't match the guidelines on material.io
angular/material 2.0.0-beta.10
The text was updated successfully, but these errors were encountered:
fix(theming): incorrect green-500 contrast color
bee76f3
As per the Material Design specifications, the 500-hue for the green palette should have a black (87% opacity) contrast color. Fixes angular#7490
fix(theming): incorrect green-500 contrast color (#7492)
c1f6ea1
Fixes #7490
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.
Sorry, something went wrong.
devversion
Successfully merging a pull request may close this issue.
Bug, feature request, or proposal:
Bug
What is the expected behavior?
That colors exactly match the color palettes on material.io guidelines.
What is the current behavior?
Sass palette $mat-green's 500 hue, has a white contrast color instead of the guideline's black color
What are the steps to reproduce?
What is the use-case or motivation for changing an existing behavior?
It doesn't match the guidelines on material.io
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
angular/material 2.0.0-beta.10
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: