- From: Mathieu Dutour via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jan 2020 18:34:15 +0000
- To: public-design-tokens-log@w3.org
> If the spec defines what lighten means, it is opinionated about what color model to use
Yeah, but you could define different function for different color model. If you don't specify what `lighten` means, you **will** end up with different tools giving different results.
The format won't define what the functions are, but the specs should. So in the format, you can reference any function, even if they aren't defined by the spec, and your tool can decide to handle it if they want to.
Just like in CSS:
```css
div {
width: grow(10px, 10);
}
```
That's a valid CSS syntax, but `grow` doesn't mean anything. You can have tools that handle it (like postcss), but that doesn't mean it's valid CSS. It's your own responsibility to make sure your use tools that know what `grow` is.
But I do agree that there shouldn't be too many functions define _a priori_, and we should wait to have a strong consensus around the definition of a function before putting it in the spec
--
GitHub Notification of comment by mathieudutour
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/1#issuecomment-580392030 using your GitHub account
Received on Thursday, 30 January 2020 18:34:17 UTC