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
Restrictions on the identifier of user-registered color spaces? #23
Comments
No, Color API spaces don't need a We don't currently have any way to bridge between We do plan to allow them to be used together, but we're not yet sure how. That said, I'm almost certain it won't be by naively merging the namespaces. Instead, I suspect that either we'll come up with an alternate syntax for referring to a Color API space by name (which would serve the same purpose as the Sorry that, as far as I can tell, this doesn't help you out with your particular issue. ^_^ |
Thanks, @tabatkins, I appreciate the insight! If I understand correctly, The HSV example in the README also hints at the idea of a custom serialization (e.g. |
No, these are programmatic modifications, at least for now. I'll open another issue about integrating the two.
Yeah, I'm not sure there are use cases for this, and I'm inclined to punt for L1. |
The CSS Color Level 4 mentions that the
@color-profile
at-rule works with<dashed-ident>
to allow the registration of additional color spaces. The current spec mentions the ability to register color spaces. Will these color spaces need to be prefixed with--
?I'm in the process of implementing generic color serialization in the culori color library and was wondering whether a color space such as Jzazbz should be serialized to a CSS color value as
color(jzazbz j a b)
orcolor(--jzazbz j a b)
, such that the color space definition can be registered by the library consumer on their web pages.The text was updated successfully, but these errors were encountered: