> Also, how would users signal their preference? There are currently three platforms that implement an explicit setting for this preference.
- In Windows 10/11: Settings > Accessibility > Visual effects > Transparency effects. - In macOS: System Preferences > Accessibility > Display > Reduce transparency. - In iOS: Settings > Accessibility > Display & Text Size > Reduce Transparency. I don't have access to Chrome OS and as such can't be sure on if there's a setting for this but based on the fact Android doesn't have one and I couldn't find documentation I've assumed there isn't. Currently the implementation is written to follow the Windows and macOS setting, and iOS can be added trivially in future once the blink development is further along on iOS. On platforms with no explicit setting users currently cannot indicate their preference. However, I would like to see browser level control of this (and other preference media queries) in future. On Monday, 24 July 2023 at 09:14:13 UTC+1 yoav...@chromium.org wrote: > I'd love to hear +Mike Taylor 's thought about this from an extra > fingerprinting bit perspective. Also, how would users signal their > preference? > > On Fri, Jul 21, 2023, 23:21 Luke <lukewa...@gmail.com> wrote: > >> Contact emailslukewa...@gmail.com, lu...@warlow.dev >> >> ExplainerNone >> >> Specification >> https://drafts.csswg.org/mediaqueries-5/#prefers-reduced-transparency >> >> Summary >> >> Adds the `prefers-reduced-transparency` feature, which lets authors adapt >> web content to user-selected preference for reduced transparency in the OS, >> such as the 'Reduce transparency' setting on macOS. Valid options are >> 'reduce' or 'no-preference'. >> >> >> Blink componentBlink>CSS >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS> >> >> Search tagscss <https://chromestatus.com/features#tags:css>, >> prefers-reduced-transparency >> <https://chromestatus.com/features#tags:prefers-reduced-transparency> >> >> TAG reviewNone >> >> TAG review statusNot applicable >> >> Risks >> >> >> Interoperability and Compatibility >> >> >> >> *Gecko*: No signal ( >> https://github.com/mozilla/standards-positions/issues/851) There is a >> separate umbrella issue for some the preference media queries (contrast, >> motion, color-scheme). They have a stale PR to add an overall positive >> position for those preference media queries. They also have an >> implementation behind a flag. It's not been enabled yet due to >> fingerprinting concerns. >> >> *WebKit*: No signal ( >> https://github.com/WebKit/standards-positions/issues/145) I have >> submitted an implementation of this feature as a PR to WebKit: >> https://github.com/WebKit/WebKit/pull/11560 >> >> *Web developers*: Positive ( >> https://blog.logrocket.com/new-media-queries-you-need-to-know) >> >> *Other signals*: >> >> Security >> >> This feature can be used for fingerprinting as it exposes a user >> preference. >> >> >> 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 >> >> This can be emulated in the Dev Tools rendering tab like other preference >> media queries. >> >> >> Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, Chrome OS, Android, and Android WebView)?Yes >> >> The feature will be supported on all platforms, but whether the user will >> be able to signal a reduced transparency preference may depend on the OS. >> >> >> Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >> ?Yes >> >> Flag name on chrome://flags#enable-experimental-web-platform-features >> >> Finch feature namePrefersReducedTransparency >> >> Requires code in //chrome?False >> >> Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1424879 >> >> Sample links >> >> https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-transparency#examples >> >> Estimated milestones >> Shipping on desktop 117 >> DevTrial on desktop 117 >> Shipping on Android 117 >> DevTrial on Android 117 >> >> 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). >> >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/5191066147356672 >> >> Links to previous Intent discussionsIntent to prototype: >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6D62B5CD-B44D-4CB1-B85A-F73DFFD6CE85%40gmail.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+...@chromium.org. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/27CA7B34-5C7E-44DE-A75D-41E6034DD833%40gmail.com >> >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/27CA7B34-5C7E-44DE-A75D-41E6034DD833%40gmail.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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e03f6ce7-9657-4c97-8337-6dc2b48983d8n%40chromium.org.
