- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Oct 2022 20:02:57 +0000
- To: public-css-archive@w3.org
> `contrast-color(wheat tbd-bg wcag2 / bisque var(--accent-color) olive sienna color(display-p3 0 1 0) maroon)` Losing the commas means the syntax becomes completely inextensible in the future; see 'counter-reset' for an example of this being bad. I'd strongly advise against it. > Foreground/background keyword options I don't recall if we considered `top`/`bottom`. They're clear, fairly short, already used, and don't have the ordering concern that `over`/`under` do. > Should we have a default (background)? I think this should be based solely on, when using whatever algo we think is most reasonable (and default, if possible), if the fg/bg decision makes a significant difference in the output. If they're usually pretty close and never terrible when done wrong-way, then sure, make it optional, no need to require something that usually won't matter. But if those aren't both true, then no, we should keep it required. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7937#issuecomment-1287383785 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 October 2022 20:02:59 UTC