-
Notifications
You must be signed in to change notification settings - Fork 22.5k
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
Move color keywords into their own page #14615
Conversation
Preview URLs
FlawsNote! 1 document with no flaws that don't need to be listed. 🎉 URL:
External URLsURL: No new external URLs URL:
(this comment was updated 2022-04-04 06:28:27.667324) |
</tbody> | ||
</table> | ||
|
||
> **Note:** The list of accepted keywords has undergone many changes during the evolution of CSS: |
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.
A lot of this feels like duplication of the notes you have preceding the table. Could be one of those things you plan on looking at later.
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.
My goal is to replace this note with regular Specifications and Browser compatibility sections but I need to restructure the bcd data for <color>
for this. (It currently is a kind of a mess)
I'm nevertheless pushing an update. I noticed navigation was not very practical and instead of saying CSS level 1 near the top, I listed the 16 colors and improved the explanation. I think the intro is better now.
@@ -7,15 +7,16 @@ tags: | |||
--- | |||
{{CSSRef}} | |||
|
|||
**Color keywords** are case-insensitive identifiers that represent a specific color, such as `red`, `blue`, `black`, or `lightseagreen`. Although the names more or less describes their respective colors, they are essentially artificial, without a strict rationale behind the names used. | |||
**Color keywords** are case-insensitive identifiers representing a specific color, such as `red`, `blue`, `black`, or `lightseagreen`. Although the names more or less describe their respective colors, they are essentially artificial, without a strict rationale behind the terms used. |
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.
FWIW I would probably have left as "that represent"
- [HTML](/en-US/docs/Web/HTML) only recognizes the 16 basic color keywords found in CSS Level 1, using a specific algorithm to convert unrecognized values (often to completely different colors). The other color keywords should only be used in CSS and [SVG](/en-US/docs/Web/SVG). | ||
- Unlike HTML, CSS will completely ignore unknown keywords. | ||
- The color keywords all represent plain, solid colors, without transparency. | ||
- [HTML](/en-US/docs/Web/HTML) only recognizes the 16 basic color keywords (`black`, `silver`, `gray`, `white`, `maroon`, `red`, `purple`, `fuchsia`, `green`, `lime`, `olive`, `yellow`, `navy`, `blue`, `teal`, and `aqua`). |
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.
FWIW I like this a lot more
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.
Thanks. Yes, this is not the final product, but happy to merge even so a "better".
Part of openwebdocs/project#92 (revamp our color guide and reference).
This PR moves the color keywords into their own page (taking them off the
<color>
page).Note that there is much more work to be done on the
<color>
page, I intentionally limited this PR by moving the color keywords only.