- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 Nov 2024 00:03:52 +0000
- To: public-css-archive@w3.org
> That is how the system is meant to work. currentColor over transparency is supposed to work as long as you do the right thing on the parent element. The point here is like it works mostly like putting a plain <div> on the page. Okay, but that's not how buttons, inputs, *or* selects work. You can safely use those over *any* background, without having to set their color/background at all, because they all have opaque backgrounds. Using transparency to mimic the appearance of buttons *in some conditions* doesn't seem great; it's certainly *novel*, and I think we need a pretty good justification for this novelty, versus the standard patterns of either "fully opaque default color" or "fully transparent". (I don't have an opinion about whether they should be opaque or transparent, I just don't like this novel "mostly transparent" style.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10857#issuecomment-2499281859 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 26 November 2024 00:03:53 UTC