Contact emails
lukewarlow...@gmail.com <mailto:lukewarlow...@gmail.com>, l...@warlow.dev 
<mailto:l...@warlow.dev>

Explainer
https://github.com/wicg/user-preference-media-features-headers/blob/main/README.md

Specification
https://wicg.github.io/user-preference-media-features-headers/#sec-ch-prefers-reduced-transparency

Summary
User Preference Media Features Client Hints Header defines a set of HTTP Client 
Hints headers around user preference media features as defined by Media Queries 
Level 5. If used as Critical Client Hints, these headers allow servers to make 
smart choices regarding, e.g., CSS inlining.

Sec-CH-Prefers-Reduced-Transparency reflects the user's 
prefers-reduced-transparency preference.


Blink component
Blink>CSS 
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS>

Motivation
CSS media queries, and specifically user preference media features like 
`prefers-reduced-transparent` or `prefers-reduced-motion`, have a potentially 
significant impact on the amount of CSS that needs to be delivered by a page, 
and on the experience the user is going to have when the page loads.

Focusing on `prefers-color-scheme`—but highlighting that the reasoning applies 
to other user preference media features as well—it is a best practice to not 
load CSS for the particular non-matching color scheme in the critical rendering 
path, and instead to initially only load the currently relevant CSS. One way of 
doing so is via `<link media>`.

However, high-traffic sites like Google Search that wish to honor user 
preference media features like `prefers-color-scheme` and that inline CSS for 
performance reasons, need to know about the preferred color scheme (or other 
user preference media features respectively) ideally at request time, so that 
the initial HTML payload already has the right CSS inlined.


Initial public proposal
https://github.com/w3c/csswg-drafts/issues/4162

Search tags
client hints <https://chromestatus.com/features#tags:client%20hints>, 
sec-ch-prefers-reduced-transparency 
<https://chromestatus.com/features#tags:sec-ch-prefers-reduced-transparency>, 
prefers-reduced-transparency 
<https://chromestatus.com/features#tags:prefers-reduced-transparency>

TAG review


TAG review status
Pending

Risks


Interoperability and Compatibility


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?


Debuggability


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


Finch feature name


Non-finch justification
None

Requires code in //chrome?
False

Tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=1466423

Estimated milestones
No milestones specified


Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/6242983812268032

Links to previous Intent discussions


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/B1ED49A6-31BF-4D28-89B3-D2973F9F12DA%40gmail.com.

Reply via email to