-
Notifications
You must be signed in to change notification settings - Fork 136
Add none keyword #327
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
Add none keyword #327
Conversation
☔ The latest upstream changes (presumably #328) made this pull request unmergeable. Please resolve the merge conflicts. |
e647027
to
9bdf3bc
Compare
02295d9
to
4582f86
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only looked at the new changes but seems reasonable. r=me with the bits below addressed.
@bors-servo delegate+ (@tiaanl this allows you to |
✌️ @tiaanl can now approve this pull request |
@bors-servo r=emilio |
📌 Commit da5ea89 has been approved by |
☀️ Test successful - checks-github |
1 similar comment
☀️ Test successful - checks-github |
For each color component, we allow the "none" keyword. The keyword will be kept in place for serialization. The "none" keyword is not allowed in the legacy syntax.
rgb
andhsl
are handled special, because they support the legacy color syntax. They also cannot be combined, because rgb cares about the type of the components, and hsl does not.