You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In general in CSS we use <custom-ident> for CSS-internal identifiers, see @namespace, @font-face, @counter-style. Color 5 proposes to use <dashed-ident> for color profile names (@color-profile), which is inconsistent. Should it be switched to <custom-ident> or is there some compelling reason why color profile names need to be different?
The text was updated successfully, but these errors were encountered:
If not handled carefully, this can result in difficulties adding new CSS-defined values; UAs have to study existing usage and gamble that there are sufficiently few author-defined identifiers in use matching the new CSS-defined one, so giving the new value a special CSS-defined meaning won’t break existing pages.
Right, we have dashed-idents specifically for the case where we're mixing them with CSS-defined idents (or would otherwise have parsing ambiguities for some other reason). This is 100% one of those cases, so dashed-ident is required.
In general in CSS we use
<custom-ident>
for CSS-internal identifiers, see@namespace
,@font-face
,@counter-style
. Color 5 proposes to use<dashed-ident>
for color profile names (@color-profile
), which is inconsistent. Should it be switched to<custom-ident>
or is there some compelling reason why color profile names need to be different?The text was updated successfully, but these errors were encountered: