- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 May 2020 22:30:03 +0000
- To: public-css-archive@w3.org
@andruud Are you familiar with the `!override` idea we talked about on the call (and on a previous call)? I haven't written it out yet (soon!), but basically if a declaration is tagged with `!override`, you track it as an additional cascaded value (essentially remembering two values for the property - one "all the values, both !override and not" and one "only the !override values"). Then, if forced-colors-mode is active, this is a property affected by forced-colors mode, *and* there's at least one !override value for the property, the !override value automatically wins. Otherwise, the normal cascade wins. Does this satisfy your circularity concerns? It should achieve the same effects as "revert at computed-value time" if the author doesn't do anything, *and* let us drop the `forced-color-adjust` property altogether, as authors can tag their own declarations with !override to win over the UA values when necessary. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4155#issuecomment-632379021 using your GitHub account
Received on Thursday, 21 May 2020 22:30:05 UTC