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.
Thanks,
Priya
------------------------------------------------------------------------
*From:* Mike Taylor <miketa...@chromium.org>
*Sent:* Tuesday, April 29, 2025 7:46 AM
*To:* Alex Russell <slightly...@chromium.org>; blink-dev
<blink-dev@chromium.org>
*Cc:* Chromestatus <ad...@cr-status.appspotmail.com>; Alison Maher
<alma...@microsoft.com>; Howard Wolosky
<howard.wolo...@microsoft.com>; Joey Arhar <jar...@chromium.org>;
Hoch Hochkeppel (HE/HIM) <mho...@microsoft.com>; Natasha Gaitonde
<nagai...@microsoft.com>; Priya Palanisamy <priya...@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 miketa...@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
priya...@microsoft.com <mailto:priya...@microsoft.com>
Explainer
None
Specification
https://drafts.csswg.org/css-ui-4/#widget-accent
<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
<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
<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
<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-visited.tentative.html>
- https://wpt.fyi/results/css/css-ui/accent-color-parsing.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-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-typed-om/the-stylepropertymap/properties/accent-color.html>
-
https://wpt.fyi/results/css/css-ui/animation/accent-color-interpolation.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 <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
<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
<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
<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
<mailto: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/b703f004-c327-460a-923f-63ebb7fa6208%40chromium.org.
