[csswg-drafts] [css-color-4] The color() function <ident> doesn't seem to be future proof (#4654)

karip has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-color-4] The color() function <ident> doesn't seem to be future proof ==
The [color()](https://www.w3.org/TR/css-color-4/#color-function) function's `<ident>` can be either a predefined colorspace or a custom identifier. Custom identifiers can't be a predefined colorspaces ('srgb', 'rec-2020', etc.): ["predefined colorspace keywords .. are excluded from this `<custom-ident>`"](https://www.w3.org/TR/css-color-4/#at-profile).

It seems that it won't be possible to add new predefined colorspaces because they could potentially break user defined custom identifiers:

Let's say I create a web page which uses my colorspace with a custom identifier 'rec-2100'. Then, the CSS working group decides to create a new predefined colorspace called 'rec-2100'. Since predefined colorspaces can't be used as custom identifiers, the new predefined colorspace will override my colorspace and breaks my web page.

Would it be better to differentiate custom identifiers with quotes or something so that they won't clash with predefined colorspaces?

Or are you certain that there will never be new predefined colorspaces? I think there is a plan to add at least [one predefined SWOP colorspace](https://github.com/w3c/csswg-drafts/issues/3449).

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4654 using your GitHub account

Received on Wednesday, 8 January 2020 09:34:16 UTC