- From: Mason Freed via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Nov 2022 22:14:21 +0000
- To: public-css-archive@w3.org
> Well, for natively-themed form controls, the accent-color should probably also control the outline color shouldn't it? The same way it might affect the border colors and so on. I don't know! I think here, too, the user assumes the focus ring is something the *page* provides, and isn't specific to the element. I feel like it'd be weird for a normally-blue focus ring to change to pink when it hit a pink-accented checkbox, for example. > The way to make `outline: auto` do the right thing while respecting `outline-color`, would be to change the initial value of `outline-color`, is that what you're proposing? So first, I meant (initially) and I think you meant here, `outline-style: auto`, not `outline:auto`, right? Since `outline` is a shorthand, I'm not sure we should add an `auto` value to that, but maybe. For `outline-style`, the spec seems pretty clear what `auto` itself means, as you pointed out. However, it says this about the other two: > As such, this specification does not define how the [outline-color](https://w3c.github.io/csswg-drafts/css-ui/#propdef-outline-color) and [outline-width](https://w3c.github.io/csswg-drafts/css-ui/#propdef-outline-width) are incorporated or used (if at all) when rendering auto style outlines. Perhaps we should amend that to say something about trying to use `outline-color` as much as possible when `outline-style: auto`? It probably can't be more specific or normative than that, since the UA style (e.g. Firefox's) might include more than one color, or gradients, etc. But I'm in favor of trying to push in that direction. -- GitHub Notification of comment by mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7761#issuecomment-1317742156 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 November 2022 23:19:17 UTC