Contact emails
gerch...@microsoft.com<mailto:gerch...@microsoft.com>, 
yshalivs...@microsoft.com<mailto:yshalivs...@microsoft.com>

Explainer
None

Specification
https://www.w3.org/TR/css-color-adjust-1

Summary

Makes the browser use the user's preferred color scheme to render the viewport 
scrollbars if the value of "page’s supported color schemes" is 'normal' or not 
specified, and the computed value of the color-scheme for the root element is 
'normal'. Viewport scrollbars can be considered to be outside the web content. 
Therefore, the user agents should honor the user's preferred color scheme when 
rendering viewport scrollbars if page authors have not explicitly specified 
support for color schemes.


Blink component
Blink>Layout>Scrollbars<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELayout%3EScrollbars>

TAG review
None

TAG review status
Not applicable

Risks

Interoperability and Compatibility

None


Gecko: No signal

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

None


Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, 
ChromeOS, Android, and Android WebView)?
Yes

Is this feature fully tested by 
web-platform-tests<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
No

Flag name on chrome://flags
None

Finch feature name
UsedColorSchemeRootScrollbars

Requires code in //chrome?
False

Tracking bug
https://issues.chromium.org/issues/40259909

Measurement
Added a use counter UsedColorSchemeRootScrollbarsDark. The counter tracks the 
number of users who have dark mode root scrollbars due to the feature. Adoption 
in Edge Stable population based on this metric is approximately 13%.

Availability expectation
Initially available in Chromium browsers.

Adoption expectation
This feature immediately affects specific use cases upon launch.

Adoption plan
This feature has been through origin trials on Edge. Other browsers adopt this 
feature to fix specific use cases.

Non-OSS dependencies

Does the feature depend on any code or APIs outside the Chromium open source 
repository and its open-source dependencies to function?

No.

Estimated milestones
Shipping on desktop
124
DevTrial on desktop
121


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/5089486318075904

Links to previous Intent discussions
Intent to prototype: 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/PH8PR00MB16366CA3D32D8ECE2C646C54A94D2%40PH8PR00MB1636.namprd00.prod.outlook.com

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 on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/LV3PR00MB17488611D88C9E41AC6A806BA95F2%40LV3PR00MB1748.namprd00.prod.outlook.com.

Reply via email to