- From: Tim Nguyen via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Nov 2024 12:49:22 +0000
- To: public-css-archive@w3.org
> > As @fantasai mentioned, you don't want to affect other uses of system colors on the page. > > Can either of you elaborate? Do you mean we don't want to change existing system color behavior? If so that's fine tho, right? We can add new ones, or am I missing something? We can't change the existing ones at least. People expect combinations like ButtonFace / ButtonText to consistently contrast and to be opaque in all modes/situations (including when overlaying a background-image) if they use them on other elements than form controls. If we re-map those to transparent colors, these assumptions no longer hold. Introducing new keywords is an option, but I don't think it's a great one, mainly because it's harder to understand due to the extra indirection, and makes it less tempting to use the defaults. If forced colors mode is the main concern, can't we just force the system colors when this is enabled? The mechanism to do this is up to the implementor, could be a media query inside the UA stylesheet, could be a `-internal-base-forced-colors` function, etc... I'm not convinced we should introduce new keywords for the sake of forced colors mode. -- GitHub Notification of comment by nt1m Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10909#issuecomment-2478742100 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 November 2024 12:49:23 UTC