Thanks! One quick follow-up if you don't mind: It's not clear whether this affects the default selection (as in, text selection) colors. Are they effected?
It does feel odd / wrong to expose an inconsistent colors between AccentColor / Highlight and form controls / selection... As an author, if I want to use the default form controls and want my custom controls to feel native, I'd expect I'd be able to use AccentColor/AccentColorText for that. That said, I understand there are more concerns about fingerprinting with those (not sure if Blink has or plans to have mitigations to prevent the native accent color from being read back from a canvas or so, if you e.g. draw a checked checkbox?). At least in Gecko we were considering making other platforms behave like windows in this area, to prevent fingerprinting the system accent color / system theme / etc... Thanks, -- Emilio On Mon, May 5, 2025, at 9:58 PM, 'Priya Palanisamy' via blink-dev wrote: > Hi Emilio, > To clarify, this feature affects ONLY form elements like Radio button, check > box, Progress bar etc., that enables user selection. These elements will take > system accent-color when the `accent-color` CSS property is not set or set to > `auto.` > > `Highlight` or `AccentColor` System Color Keywords are NOT affected by this > change. > > Thanks, > Priya > > > *From:* Emilio Cobos Álvarez <emi...@crisal.io> > *Sent:* Saturday, May 3, 2025 5:29 AM > *To:* Daniel Clark <dan...@microsoft.com>; blink-dev <blink-dev@chromium.org> > *Cc:* Priya Palanisamy <priya...@microsoft.com>; yoav...@chromium.org > <yoavwe...@chromium.org>; mike...@chromium.org <miketa...@chromium.org>; > Chromestatus <ad...@cr-status.appspotmail.com>; Alison Maher > <alma...@microsoft.com>; Howard Wolosky <howard.wolo...@microsoft.com>; > jar...@chromium.org <jar...@chromium.org>; Hoch Hochkeppel (HE/HIM) > <mho...@microsoft.com>; Natasha Gaitonde <nagai...@microsoft.com>; > sligh...@chromium.org <slightly...@chromium.org> > *Subject:* Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: System accent > color for accent-color property. > > > You don't often get email from emi...@crisal.io. Learn why this is important > <https://aka.ms/LearnAboutSenderIdentification> > > Curious, is the idea to do this on Windows too? (I assume that given > Microsoft is implementing, it is). > > Is this also going to affect things like selection colors and the Highlight / > AccentColor system colors? > > For context, the reason it doesn't work on Firefox is that we had to turn it > off because grey accent colors were confusing to users and such, see > https://bugzilla.mozilla.org/show_bug.cgi?id=1776588 for some discussion. > > -- Emilio > > On Fri, May 2, 2025, at 8:02 PM, 'Dan Clark' via blink-dev wrote: >> LGTM3 >> >> It turns out from the WebKit position thread that this is already shipped >> there as well. Request to use platform accent color for accent-color >> property as default option · Issue #485 · WebKit/standards-positions >> <https://github.com/WebKit/standards-positions/issues/485> >> >> -- Dan >> On Wednesday, April 30, 2025 at 10:07:36 AM UTC-7 Priya Palanisamy wrote: >>> Hi Yoav, >>> >>> For >>> >>" Would that change current rendering of sites that don't set any >>> accent-color?" >>> *Yes*, when accent-color is not set, it is basically set to default value >>> "auto", which will take system's accent color with this change. >>> On Wednesday, April 30, 2025 at 5:36:31 AM UTC-7 Yoav Weiss (@Shopify) >>> wrote: >>>> On Wednesday, April 30, 2025 at 1:07:19 PM UTC+2 Mike Taylor wrote: >>>>> __ >>>>> Or rather, LGTM2 >>>>> >>>>> >>>>> >>>>> On 4/30/25 7:06 AM, Mike Taylor wrote: >>>>>> Thanks, >>>>>> >>>>>> >>>>>> >>>>>> LGTM1 >>>>>> >>>>>> On 4/29/25 1:45 PM, Priya Palanisamy wrote: >>>>>>> Hi Mike, >>>>>>> >>>>>>> Yes, the I2S proposes using the system accent color when the value is >>>>>>> set to "auto". To clarify, "auto" is also the default option if no >>>>>>> value is provided. Therefore, if the accent-color is not explicitly >>>>>>> set, the form elements will automatically use the system accent color >>>>>>> by default. >>>> >>>> Would that change current rendering of sites that don't set any >>>> accent-color? >>>> >>>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> Priya >>>>>>> >>>>>>> *From:* Mike Taylor <mike...@chromium.org> >>>>>>> *Sent:* Tuesday, April 29, 2025 7:46 AM >>>>>>> *To:* Alex Russell <sligh...@chromium.org>; blink-dev >>>>>>> <blin...@chromium.org> >>>>>>> *Cc:* Chromestatus <ad...@cr-status.appspotmail.com>; Alison Maher >>>>>>> <alm...@microsoft.com>; Howard Wolosky <howard....@microsoft.com>; Joey >>>>>>> Arhar <jar...@chromium.org>; Hoch Hochkeppel (HE/HIM) >>>>>>> <mho...@microsoft.com>; Natasha Gaitonde <naga...@microsoft.com>; Priya >>>>>>> Palanisamy <priy...@microsoft.com> >>>>>>> *Subject:* [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: System accent >>>>>>> color for accent-color property. >>>>>>> >>>>>>> >>>>>>> You don't often get email from mike...@chromium.org. Learn why this is >>>>>>> important <https://aka.ms/LearnAboutSenderIdentification> >>>>>>> >>>>>>> Just to clarify, this intent proposes to add an `auto` value to >>>>>>> accept-color, that picks up the system accent-color. Do I have that >>>>>>> right? >>>>>>> >>>>>>> On 4/28/25 2:15 PM, Alex Russell wrote: >>>>>>>> Hey Priya, >>>>>>>> >>>>>>>> Can we make sure to request explicit signals from WebKit? Thanks. >>>>>>>> >>>>>>>> LGTM1 modulo that nit. >>>>>>>> >>>>>>>> Best, >>>>>>>> >>>>>>>> Alex >>>>>>>> >>>>>>>> On Wednesday, April 23, 2025 at 10:49:26 AM UTC-7 Chromestatus wrote: >>>>>>>>> Contact emails priy...@microsoft.com >>>>>>>>> >>>>>>>>> Explainer None >>>>>>>>> >>>>>>>>> Specification https://drafts.csswg.org/css-ui-4/#widget-accent >>>>>>>>> >>>>>>>>> Summary >>>>>>>>> This feature empowers web developers to enhance the visual appeal of >>>>>>>>> their websites by leveraging the operating system's accent color for >>>>>>>>> form elements. By utilizing the "accent-color" CSS property, >>>>>>>>> developers can ensure that form elements such as checkboxes, radio >>>>>>>>> buttons, and progress bars automatically adopt the accent color >>>>>>>>> defined by the user's operating system. This feature is an >>>>>>>>> enhancement to existing feature that is already shipped in Chromium: >>>>>>>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/WwYkLjbGhoA >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Blink component Blink>CSS >>>>>>>>> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ECSS%22> >>>>>>>>> >>>>>>>>> Search tags accent-color <http:///features#tags:accent-color>, accent >>>>>>>>> <http:///features#tags:accent>, color <http:///features#tags:color>, >>>>>>>>> system accent color <http:///features#tags:system%20accent%20color> >>>>>>>>> >>>>>>>>> TAG review None >>>>>>>>> >>>>>>>>> TAG review status Not applicable >>>>>>>>> >>>>>>>>> Risks >>>>>>>>> >>>>>>>>> >>>>>>>>> Interoperability and Compatibility >>>>>>>>> None >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> *Gecko*: Shipped/Shipping Firefox currently supports this feature on >>>>>>>>> Mac and Linux platforms. >>>>>>>>> >>>>>>>>> *WebKit*: No signal >>>>>>>>> >>>>>>>>> *Web developers*: No signals >>>>>>>>> >>>>>>>>> *Other signals*: >>>>>>>>> >>>>>>>>> WebView application risks >>>>>>>>> Does this intent deprecate or change behavior of existing APIs, such >>>>>>>>> that it has potentially high risk for Android WebView-based >>>>>>>>> applications? >>>>>>>>> >>>>>>>>> None >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Debuggability >>>>>>>>> When the platform's accent color is utilized for the "accent-color" >>>>>>>>> CSS property, either due to the absence of a specified value or when >>>>>>>>> set to "auto," the getComputedStyle() JS function returns "auto" >>>>>>>>> instead of the actual hexadecimal value of the color being applied. >>>>>>>>> Related link: https://github.com/w3c/csswg-drafts/issues/6158 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Will this feature be supported on all six Blink platforms (Windows, >>>>>>>>> Mac, Linux, ChromeOS, Android, and Android WebView)? No >>>>>>>>> This feature is currently supported on Windows, macOS, and ChromeOS. >>>>>>>>> Future work for Linux is planned and can be tracked at the following >>>>>>>>> link: https://issues.chromium.org/issues/391917949. Android features >>>>>>>>> a setting for accent color, and we plan to add support for Android in >>>>>>>>> the future. The strategy is to release this feature incrementally, >>>>>>>>> allowing web developers to provide feedback and assess the necessity >>>>>>>>> of allocating additional resources for other less requested platforms. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Is this feature fully tested by web-platform-tests >>>>>>>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>? >>>>>>>>> Yes >>>>>>>>> - >>>>>>>>> https://wpt.fyi/results/css/css-ui/accent-color-visited.tentative.html >>>>>>>>> - https://wpt.fyi/results/css/css-ui/accent-color-parsing.html - >>>>>>>>> https://wpt.fyi/results/css/css-ui/accent-color-computed.html - >>>>>>>>> https://wpt.fyi/results/css/css-typed-om/the-stylepropertymap/properties/accent-color.html >>>>>>>>> - >>>>>>>>> https://wpt.fyi/results/css/css-ui/animation/accent-color-interpolation.html >>>>>>>>> Note: The provided links are WPT for the accent-color property, >>>>>>>>> including scenarios where the value is set to "auto." This feature >>>>>>>>> relies on the platform's accent color and necessitates a WebDriver >>>>>>>>> extension to simulate the accent-color property accurately. To ensure >>>>>>>>> consistent testing with WPT, we would need to look into WebDriver API >>>>>>>>> to support this functionality properly. >>>>>>>>> >>>>>>> Are there any bugs to track this WebDriver follow-up work? >>>>>>>>> >>>>>>>>> >>>>>>>>> Flag name on about://flags None >>>>>>>>> >>>>>>>>> Finch feature name CSSSystemAccentColor >>>>>>>>> >>>>>>>>> Rollout plan Will ship enabled for all users >>>>>>>>> >>>>>>>>> Requires code in //chrome? False >>>>>>>>> >>>>>>>>> Tracking bug https://issues.chromium.org/issues/40764875 >>>>>>>>> >>>>>>>>> Estimated milestones Shipping on desktop 137 >>>>>>>>> >>>>>>>>> Anticipated spec changes >>>>>>>>> Open questions about a feature may be a source of future web compat >>>>>>>>> or interop issues. Please list open issues (e.g. links to known >>>>>>>>> github issues in the project for the feature specification) whose >>>>>>>>> resolution may introduce web compat/interop risk (e.g., changing to >>>>>>>>> naming or structure of the API in a non-backward-compatible way). >>>>>>>>> >>>>>>>>> None >>>>>>>>> >>>>>>>>> Link to entry on the Chrome Platform Status >>>>>>>>> https://chromestatus.com/feature/6548224737017856?gate=5857060564238336 >>>>>>>>> >>>>>>>>> Links to previous Intent discussions Intent to Prototype: >>>>>>>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/q9zf-frdewo/m/zxw2HuzGAQAJ >>>>>>>>> >>>>>>>>> >>>>>>>>> This intent message was generated by Chrome Platform Status >>>>>>>>> <https://chromestatus.com/>. >>>>>>>> -- >>>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "blink-dev" group. >>>>>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>>>>> an email to blink-dev+unsubscr...@chromium.org. >>>>>>>> >>>>>>>> To view this discussion visit >>>>>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/54317d12-4347-4265-8f06-c9d1dd795110n%40chromium.org >>>>>>>> >>>>>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/54317d12-4347-4265-8f06-c9d1dd795110n%40chromium.org?utm_medium=email&utm_source=footer>. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to blink-dev+unsubscr...@chromium.org. >> To view this discussion visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4dfca947-254a-47b2-885e-164a71f90b9cn%40chromium.org >> >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4dfca947-254a-47b2-885e-164a71f90b9cn%40chromium.org?utm_medium=email&utm_source=footer>. > > > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/MN6PR00MB2408F3ABDFC3247DDC754E9DCF8E2%40MN6PR00MB2408.namprd00.prod.outlook.com > > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/MN6PR00MB2408F3ABDFC3247DDC754E9DCF8E2%40MN6PR00MB2408.namprd00.prod.outlook.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/3ad95b86-de2d-4920-a8f7-4af1c0b6b11d%40app.fastmail.com.
