- From: x-Jake-x via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Oct 2020 09:16:16 +0000
- To: public-css-archive@w3.org
Is there any chance that we can do both A and B without breaking the implementation bank?
`Value: <color>+` could be `Value: [hint] <color>+`
where we expect the UA to render the colors specified consistently as expected (how to define the various parts of a control and colors for those {foreground/background/primary/whatever} can be discussed later),
_**UNLESS**_
the `hint` keyword is specified first, in which case we give the UA a wider range of decision about how to apply the `accent-color`(s) within its own styling.
This way, we can have _**both**_ consistency where we need it for mission-critical applications (think the professional version of your web application distributed to clients), or simply a hint of an accent where we don't feel like using default accents (to avoid explicitly testing and styling colors to achieve a proper contrast).
--
GitHub Notification of comment by x-Jake-x
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5480#issuecomment-704141080 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 6 October 2020 09:16:18 UTC