- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Nov 2022 17:50:08 +0000
- To: public-css-archive@w3.org
> I'm curious about your comment that outline-style: auto is intended to be the accent color - isn't outline-style just the style (dotted, solid, etc.) of the outline? `outline-style: auto`, when originally implemented, was the OS-native outline. In fact the spec still has: > The auto value permits the user agent to render a custom outline style, typically a style which is either a user interface default for the platform, or perhaps a style that is richer than can be described in detail in CSS, e.g. a rounded edge outline with semi-translucent outer pixels that appears to glow. So when implementing `accent-color`, I made `outline-style: auto` follow it so that the outline color of widgets was consistent. > Setting outline-style:auto disables the focus ring painting behavior and just turns on the default outline (black 1.5px solid). But this feels fairly easy and works well, I'm not sure why we'd want to push toward accent-color for outlines. Well, in Gecko `outline-style: auto` is not just an alias for `black 1.5px solid`. For us, it has two segments (one of 2px, one of 1px) of different colors (accent color + accent-foreground color). The default UA sheet in the HTML spec has: ``` :focus-visible { outline: auto; } ``` That really expands to `outline-style: auto; outline-color: currentColor; ...`. I don't think `outline: auto` should force black (or lose colors) of the default outline. -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7761#issuecomment-1303947615 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 November 2022 17:50:15 UTC