Repository navigation
[css-values] unify CSS wide keywords and defaulting keywords #7170
Description
These keyword definitions are currently scattered throughout the specification, making it easy for other CSS parsers or engine implementers to miss them. e.g.
var wideKeywords = map[string]bool{
"initial": true,
"inherit": true,
"unset": true,
}match &*value.to_ascii_lowercase() {
"initial" | "inherit" | "unset" | "revert" | "default" => {
return Err(Error::new(span, ErrorKind::InvalidCustomIdent(raw)));
}
_ => {}
}const globalKeywords = ['inherit', 'initial', 'unset'];css-values-4
https://www.w3.org/TR/css-values-4/#common-keywords
Defined:
initialinheritunset
css-cascade-4
https://drafts.csswg.org/css-cascade/#defaulting-keywords
Defined:
initialinheritunsetrevert
css-cascade-5
https://drafts.csswg.org/css-cascade-5/#revert-layer
Defined:
initialinheritunsetrevertrevert-layer
css-values-4
https://www.w3.org/TR/css-values-4/#ref-for-css-wide-keywords
The CSS-wide keywords are not valid
<custom-ident>s. Thedefaultkeyword is reserved and is also not a valid<custom-ident>
There is a default keyword.
Activity
tabatkins commentedon Mar 25, 2022
The definitions are already unified in the Cascade specs (and later levels replace preceding levels, so Cascade 5 is the canonical definition). Values merely mentions them, and points to Cascade for their definition; Fonts mentions them in an example (including the reserved "default" keyword)
yisibl commentedon Mar 27, 2022
@tabatkins Thank you for your reply.
Yes, the CSS fonts spec mentions the terms
common-keywords|CSS-wide keyword, so can we change them all toCSS-wide keywordin Cascade 5? Too many terms can be confusing and detrimental to communication.Also is it possible to add the "default" keyword to the
Explicit Defaultingsection in Cascade 5?fantasai commentedon Oct 10, 2022
Hi @yisibl, we've refactored the spec text around CSS-wide keywords in 9b95cab
For “default”, this is merely excluded from the
<custom-ident>production, since it is not a valid CSS-wide keyword anywhere. We are also discussing adding additional keywords to the<custom-ident>exclusion list in #7431.Closing out this issue, but let us know if there are any remaining problem.