- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Oct 2024 20:26:42 +0000
- To: public-css-archive@w3.org
More directly, look at *both* of the images in the OP. The *second* one is readable, because it uses a partially-transparent black + a blur. The *first* is completely unreadable, because it has white text overlapping a white or nearly-white page. While authors are of course free to produce unreadable content on their own, we try to avoid giving them abilities that make it easy for things to become unreadable *by accident*. But overall, I echo @Loirooriol in requesting examples of actual use-cases. *Applications* can get value out of transparent backgrounds because they can *also* suppress all the *other* window decorations, and designate custom areas to be grabbable/etc; WinAmp is the classic example of putting this ability to good use. But webpages can't do that; even if the page is transparent, the tab/UI bar will be opaque, rectangular, and floating up there at the top. It's much less obvious what useful things one can do under that constraint. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7281#issuecomment-2436277406 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 24 October 2024 20:26:43 UTC