Re: [csswg-drafts] [css-variables?] Higher level custom properties that control multiple declarations (#5624)

The CSS Working Group just discussed `[css-variables?] Higher level custom properties that control multiple declarations`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-variables?] Higher level custom properties that control multiple declarations<br>
&lt;jensimmons> Does that mean we get a CSS 2020 in 2020??<br>
&lt;astearns> just barely<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/5624<br>
&lt;dael> leaverou: I didn't explicitly add this. WE discussed last time and didn't get resolution. Interesting discussion in issue and off GH<br>
&lt;leaverou> https://github.com/w3c/csswg-drafts/issues/5624#issuecomment-746339609<br>
&lt;dael> leaverou: I summerized current state in ^ comment<br>
&lt;dael> leaverou: Summary: It looks like best course of action for block conditionals. Can't use pseudo class, casuse issues. If if() cascades have to carry extra context and increases too much complexity<br>
&lt;dael> leaverou: Best is impl if based on idea of desugering to inline if calls and take into account properties in same rule. example in comment<br>
&lt;dael> leaverou: Rasises some issues b/c certain values eval differently depending on prop. Hasn't come up that much. Length in some MQs<br>
&lt;dael> leaverou: For example, ones we could come up with TabAtkins is %, em values, rem, lh, rlh, currentColor.<br>
&lt;chris> rrsagent, here<br>
&lt;RRSAgent> See https://www.w3.org/2020/12/16-css-irc#T17-34-13-1<br>
&lt;dael> leaverou: Problem. If it desugars to inline if calls nad conditional has relative values you may have cases where part of rule eval to true and a part of false. Example in comment.<br>
&lt;dael> leaverou: Agreed don't want partial applicaitons. How to solve?<br>
&lt;dael> leaverou: Came up with defining how these relative values would be evaluated. cureentColor is as if in color and so on. New inline conditional function to desugar iff<br>
&lt;dael> leaverou: Doesn't sound good, but couldn't come with better<br>
&lt;dael> leaverou: Addresses single conditional. Css nesting has same partial applicaiton problme. May have condition true for a rule but not decendnents.<br>
&lt;Rossen_> q?<br>
&lt;dael> leaverou: Might have var warning = on and a value for --warning on parent and different value on the child<br>
&lt;dael> leaverou: You again have @if block applied paritially<br>
&lt;dael> leaverou: Not sure if there's a way to address this. Couldn't come up with anything but just discussed yesterday. Don't know if there are ideas<br>
&lt;dael> fantasai: What do you do if content has if clause with a property that effect evaluation. if on a em and evaluate em against font size<br>
&lt;dael> leaverou: Can you put example in IRC?<br>
&lt;fantasai> @if (var(...) > 1em) { font-size: 35pt; }<br>
&lt;dael> leaverou: I see<br>
&lt;dael> leaverou: I'm not sure<br>
&lt;dael> leaverou: What would you suggest should happen?<br>
&lt;dael> leaverou: It's basically same as if you have inline if<br>
&lt;dael> Rossen_: In interest of time, are we ready to resolve or should we take it back to GH and continue there?<br>
&lt;dael> leaverou: I suppose we could go back to issue<br>
&lt;dael> Rossen_: Let's do that. Let's continue discussing there. I was hoping we were closer to resolution then we are. We'll come back<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 16 December 2020 17:39:21 UTC