- From: Mason Freed via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Mar 2025 17:52:33 +0000
- To: public-css-archive@w3.org
> As Tim mentioned, the format of these controls is controlled by i18n requirements, and we don't want the author to be styling with assumptions that may turn out to be true. So I lean towards not making the separators distinguishable or customizable in terms of their content or their positions. (These aspects therefore don't need to be controllable via CSS.) That's fair, and as I said in the OP, I do see the point of architecting it this way. I just don't know how a developer would e.g. make the Month a different color from the Day. Or other simple things that developers might want to do. E.g. make the "date" fields/separators one color and the "time" fields/separators another color. Or font size. Or whatever. > Composability with new control features should be handled through additions to HTML, which can then be exposed through new CSS pseudo-elements, but that's a separate discussion from introducing pseudo-elements for existing parts of existing controls. I'd submit that developers use *both* CSS and HTML. We shouldn't be designing only half the solution just because there are two standards in two different standards bodies. Hopefully we can use [the joint forms task force meetings](https://github.com/whatwg/html/issues/11109) for this purpose, perhaps? -- GitHub Notification of comment by mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11852#issuecomment-2725384520 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 14 March 2025 17:52:34 UTC