W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2020

Re: [csswg-drafts] [accent-color] Should interoperability be a goal for the `accent-color` spec? (#5480)

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Sat, 29 Aug 2020 09:41:04 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-683265814-1598694063-sysbot+gh@w3.org>
I was intrigued by one thing fantasai proposed during the meeting, which might help strike the right balance here.

Based on the same syntax as today, you could say:

`accent-color: dark-blue, light-blue;`

But unlike what the current version suggests, this would not (necessarily) mean a request to set the accent/backgroundy color to dark blue AND the contrasting/foregroundy color to light-blue, but rather to set the accent/backgroundy color to dark blue OR the contrasting/foregroundy color light-blue. Which one gets used depends on which part of the native control is normally accented.

If the native control actually uses two distinct colors, the UA would probably use both, but in typical case where only one part is accented, the author wouldn't be telling the UA which part to use the accent color on, merely providing appropriate colors to use.

And if you only provide one, the other is synthesized, but the pair is still used to pick the right color from.

That way, we neither insist on accenting the "wrong" part of the control (according to platform conventions), nor end up with the color used in the wrong place and failing at contrast.

-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5480#issuecomment-683265814 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 29 August 2020 09:41:06 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:13 UTC