- From: Brent Jett via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Dec 2024 16:34:08 +0000
- To: public-css-archive@w3.org
Can I ask is the desire of the proposal really to expose total transparency to the browser or rather to allow elements on the page to adopt appearances that native applications today can? MacOS apps often adopt a vibrant (blurred + increased saturation) underneath sidebars while content backgrounds stay opaque or simply tinted. These provided materials also obey system settings like allowing window tinting and light/dark modes so querying `prefers-reduced-transparency` and `prefers-color-scheme` should probably be part of the conversation too. With total transparency you're still going to have a drop shadow and/or a border around the window provided by the OS, as well as the browser chrome so I'm not sure exposing it really gets us to the goal of making the page feel more appropriate to the platform and more native. My suggestion, instead, would be to offer some standardized (cause not everyone is on a mac) computed background appearances that any element on the page could adopt (including the root) to get the effect of punching through the window without even needing to set total transparency on the root. Maybe its a scale of varying vibrancies for uses like primary content vs nav or auxiliary content (similar to how we have System Colors provided by the OS now). These predefined appearances could offer a degree of contrast needed for semi-transparency and a11y but still bring in the feel of the environment similar to native apps. -- GitHub Notification of comment by brentjett Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7281#issuecomment-2536497092 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 December 2024 16:34:09 UTC