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;dael> github: https://github.com/w3c/csswg-drafts/issues/5624<br>
&lt;dael> Rossen_: Before we go into details, leaverou_ is this ready?<br>
&lt;dael> leaverou_: Is TabAtkins on?<br>
&lt;dael> leaverou_: To remond people use case is web components forced to use presentational attributes, even thought ag guidline. custom properties can only contain frag and often need higher level keywords<br>
&lt;dael> leaverou_: Been exploring how would be possible. First idea was to have an @if block. Had a breakout with fantasai and TabAtkins and realized what if block was trying to do is replicate selector logic b/c can't use selectors for omputed style. Had an idea which might make more impl-able<br>
&lt;Rossen_> q?<br>
&lt;dael> leaverou_: TabAtkins suggested new type of custom property resolved earlier in cascade which only has keywords or numbers. TabAtkins do you want to desc?<br>
&lt;dael> TabAtkins: Preface this that it's a possibility here. I think it's a useful use case.<br>
&lt;dael> Rossen_: Let me pause you. Is this issue ready for resolution? Or to bring WG back to point of current thinking?<br>
&lt;dael> TabAtkins: Get people informed about issue to get more eyes. Not seeking resolution<br>
&lt;dael> Rossen_: Thanks<br>
&lt;dael> TabAtkins: Idea I have is, new custom property. compst property<br>
&lt;dael> TabAtkins: Can be set like custom property, but can be selected on. Can do &lt; or >.<br>
&lt;dael> TabAtkins: Way you avoid problems is do sep cascade pass to resolve compst properties and treat them as not matching. You set compst and then do everything else. Avoids loops, but lets you pass properties through the tree<br>
&lt;dael> TabAtkins: Can set them on the light dom, will fall into shadows. Can match based on them.<br>
&lt;dael> TabAtkins: This is a possiblity. Would like eyes. Fear is 2nd pass like this is a lot of expense.<br>
&lt;dael> TabAtkins: Possible other ways to solve. Lots of space there, want help exploring and finding how ot make this better for users of custom elements<br>
&lt;dael> leaverou_: Hope we can solve w/o resorting to attributes since we're trying to move away from those. Making attribute selectors more powerful doesn't solve issue<br>
&lt;dael> TabAtkins: Open to a lot of possibilities. WOuld like attention paid so we can progress<br>
&lt;dael> Rossen_: Anything else we can do to attract attention?<br>
&lt;dael> Rossen_: Please take a look. Important issue and worth solving<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-801229724 using your GitHub account


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

Received on Wednesday, 17 March 2021 16:33:03 UTC