- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 May 2025 18:51:15 +0000
- To: public-css-archive@w3.org
(Apologies for having had to miss this meeting, and not seeing the resolutions until now.) I don't understand the third resolution. Forced Colors Mode has obvious, author-visible effects on the properties it affects. This set of properties needs to be interoperable between browsers; thus, it needs to be specified in some way. We do not currently have a definition anywhere else of what "color properties" are that we can lean on. This means that moving the existing list to a note just... removes necessary normative text. We do that "list in a note" thing when it's helpful to list out a category that is defined elsewhere (especially when it's *diffused*, like each property defines itself as being in the category or not). But in this case the list *is* the canonical definition. We can add a note about the listed set being something that will grow over time, and thus possibly not being *complete* at any given time, but the goal *should* be to keep it complete. Regardless, the current list is a required bit of normative definition, so I object to the resolution as it stands. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11857#issuecomment-2855589877 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 6 May 2025 18:51:17 UTC