- From: Roel N via GitHub <sysbot+gh@w3.org>
- Date: Tue, 03 Jul 2018 12:30:30 +0000
- To: public-css-archive@w3.org
Thanks for the work, everyone! 🍰
I don't know if it's important, but it feels kinda weird to always be overriding something existing when applying your own. I guess it'd _work_, but if you want to set all three colors of [Bixa Color](https://bixacolor.com) it feels weird to first have to appoint some random existing palette:
```
@font-palette-values BixaGreen {
font-family: Bixa Color;
base-palette: 'Hot pink'; /* completely irrelevant */
override-color:
1 green,
2 limegreen,
3 palegreen;
}
```
Maybe when setting a custom palette not based on another, you could set `base-palette: none` or leave out `base-palette` altogether (where all colors could default to `currentColor`).
Some name bikeshedding: would it be in alignment with other CSS like `border-color`, `background-color` etc. to call it `palette-color`? Or maybe simply `layer-color`? It wouldn't be stressing the overriding so much.
--
GitHub Notification of comment by RoelN
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1125#issuecomment-402139016 using your GitHub account
Received on Tuesday, 3 July 2018 12:30:52 UTC