- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 May 2020 21:17:12 +0000
- To: public-css-archive@w3.org
> However, I was under the impression that we wanted a way to disable forced colors for entire subtrees, in which case !override doesn't sound very practical? That's what f-c-a *did*, but it wasn't necessarily what was *required*. If you can target the subtree with selectors, you can hit all the necessary color properties with !override, and achieve the same thing. > Why cascade !override separately if forced-color-adjust doesn't exist? If forced-color-adjust doesn't exist, we're automatically not depending on computed-value time anymore, so !override might as well be a normal priority in the cascade. I don't understand the question; !override and f-c-a have nothing to do with each other. We can't have !override be another priority level; it's meant to be used in the UA stylesheet to implement forced-colors mode, after all, and it wouldn't make sense to have those rules always win. It's also meant to be used by authors to *override* the UA stylesheet where necessary, and it seems like it would be bad for usability to have it mess up the author's normal specificity when forced-colors mode isn't active. > Cascading multiple values for each property seems like an unsustainable pattern. As @FremyCompany points out we're already doing this in practice for colors, so this would mean we'd now need to cascade four values per color: :visited regular, :visited !override, unvisited regular, unvisited !override). We should IMO avoid this completely. Oh, indeed, it can't be done very much. Note that I'm still hopeful [we can fixed the :visited problem](https://github.com/w3c/csswg-drafts/issues/3012#issuecomment-467327462) (unfortunately Emil left Google, and Alex has been very busy with other things), so we'd ideally just go back to the two cascaded values rather than four. ^_^ ----- *That all said*, if you do think that revert-at-computed-value-time is fine after all, then I guess we don't need to solve anything with !override and we'll be fine. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4155#issuecomment-634284067 using your GitHub account
Received on Tuesday, 26 May 2020 21:17:13 UTC