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

> The current proposed spec does not work; it will give results - such as accent-color: black white giving a checkbox with a white background in some browsers and a black background in others - which make the property effectively useless for authors to actually match the controls to their page in a way that reads properly.

I think we have a slight disagreement here. I don't think authors should expect something more of this property than "take the platform ui and change its blue color tint to another tint" and not "make it look a specific way" because if this is the latter they want they can already do that by changing the background/other properties of the various pseudo elements.

I strongly believe that unformizing when the accent color is used as background or not is not a reasonable goal. Chrome for instance switches this when a checkbox is checked. That's not the natural situation in most platforms. While I respect that choice, I don't see how it would be reasonable to enforce that choice to all platforms.

Based on this, it would seem we don't have an agreement on what this property would do at all at the moment, since we are chasing different goals it would seem.

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 30 September 2020 18:32:42 UTC