Re: [csswg-drafts] [css-cascade-4] Revert at computed-value time (#4155)

The CSS Working Group just discussed `[css-cascade-4] Revert at computed-value time`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-cascade-4] Revert at computed-value time<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4155<br>
&lt;gregwhitworth> yeah, can we at least do anatomy investigation in Open UI for this?<br>
&lt;dael> Rossen_: Brought up by Anders who would be best to summarize.<br>
&lt;dael> Rossen_: Base of issue is when and how do properties overwritten by forced colors get reverted<br>
&lt;dael> Rossen_: Based on the issue there is a pushback against if the revert rules can apply at computed value time and if this creates dependency between properties and the way revert and override work<br>
&lt;dael> Rossen_: Couple weeks ago took a resolution where we introduced the !override that can be used to override all the properties and all the adjust properties. At that point forced-colors-adjust property is not needed<br>
&lt;dael> Rossen_: Questioning if this issue will go away and we can close no change needed<br>
&lt;dael> Rossen_: Noted TabAtkins and fantasai as you made edits in this space you may or may not have gotten to this work. Can you tell us where you are with this?<br>
&lt;dael> TabAtkins: We haven't gotten to it so not comfortable with details yet.<br>
&lt;dael> Rossen_: On the face value would you think if we had !override (tbd name) specified and impl would that simply allow us to resolve this issue?<br>
&lt;fremy> q+<br>
&lt;dael> TabAtkins: Given that this is the default...whenever forced-color sis auto the UA stylesheet overrides. This is about effects of forced-color-adjust mode. The property just lets you turn things off. THe revert is what happens by default not something the author turns on<br>
&lt;dael> Rossen_: Yeah. My hope was we could use !override UA declaration instead of current revert<br>
&lt;dael> TabAtkins: mmmm...possibly<br>
&lt;dael> TabAtkins: If UA hid it behind MQ maybe<br>
&lt;TabAtkins> And then authors could use !override to win over the UA style when necessary...<br>
&lt;gregwhitworth> emilio: I added a comment regarding the Open UI work to the issue: https://github.com/w3c/csswg-drafts/issues/5049#issuecomment-631582242  Feel free to setup some time with me so we can begin defining that and inform the psuedo element naming and if there is need for anything else<br>
&lt;dael> Rossen_: If UA spec color with !override forced-color and no user style matched with the eq you have the forced-color. If user wants to expose they can. That's why going down the path that override will solve this issue as well.<br>
&lt;dael> Rossen_: Given we don't have Anders on I'm fine pushing this by a week to see if we can make progress<br>
&lt;Rossen_> ack f<br>
&lt;dael> fremy: Quick note- Basically revert at computed time kind of does exist with :visited. We have stored in browser real style for rendering and style for :visited. If I understand spec we only need it for 2 properties, color and bg-color. Doesn't sound like a huge deal<br>
&lt;dael> fremy: Doesn't seem complex. Examples in issue don't seem like reason examples. They're crazy scenarios. Works for scanrios in the spec right now.<br>
&lt;dael> Rossen_: I think we won't be able to make progress o nthis issue<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4155#issuecomment-631584762 using your GitHub account

Received on Wednesday, 20 May 2020 16:29:33 UTC