Re: [csswg-drafts] [css-pseudo] Custom properties on :root (#6641)

The CSS Working Group just discussed `[css-pseudo] Custom properties on :root`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> fantasai: I guess this was question about can we use custom properties on ::selection etc.<br>
&lt;dael> fantasai: There's 3 approaches which each have a major downside<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/6641#issuecomment-1404031937<br>
&lt;fantasai> body::selection inherits from html::selection<br>
&lt;fantasai> not from body itself<br>
&lt;dael> fantasai: 1. is to have the root::selection inherit from :root. Highlight pseudo elements inherit through their own tree. body::selection inherits from html::selection<br>
&lt;fantasai> :root::selection inherits from :root<br>
&lt;dael> fantasai: Option 1 is have root highlights inherit from root.<br>
&lt;dael> fantasai: Second is custom prop inherit from originating element where others inherit from highlight parent.<br>
&lt;dael> fantasai: 3rd is ignore custom prop on the highlight but when we use var look at originating<br>
&lt;dael> fantasai: Downside to 1 is if custom value changes in a highlight tree the subtrees won't know<br>
&lt;dael> fantasai: Downside to the second is inherit from 2 sources is hard to implement. I remember it was hard with first-line<br>
&lt;dael> fantasai: Downside to 3rd is if you set a custom property on the highlight and use it on the same property it won't look at the value you just set<br>
&lt;Rossen_> q?<br>
&lt;dael> fantasai: Question to the WG is which approach if any do we want to take<br>
&lt;dael> Rossen_: Opinions?<br>
&lt;dael> florian: I'm thinking having custom and regular properties inherit differently doesn't play nice with having custom prop polyfill regular ones. That would argue against option 2<br>
&lt;dael> florian: All options seem to have author-facing downsides so can't rule based on priority of constituency<br>
&lt;dael> Rossen_: Is there a path forward where we can adapt option 3 to work for highlight?<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/6641#issuecomment-1404031937<br>
&lt;dael> fantasai: We can make all the options work, question of which has the least downsides<br>
&lt;dael> florian: Should we get author feedback and see what they'd find most or least helpful? I'd just be guessing<br>
&lt;dael> Rossen_: If that's what's holding us back we might<br>
&lt;dael> fantasai: Could be helpful to get feedback from sanketj team b/c more useful for custom highlights than ::selection<br>
&lt;dael> sanketj: I think we'll need to look into this a little bit more. No preference right now. We can follow-up<br>
&lt;dael> Rossen_: That doesn't inspire confidence to resolve today. We may have to come back to this once there are stronger opinions. Will that work fantasai?<br>
&lt;dael> fantasai: I don't think it's urgent, but good to figure out<br>
&lt;dael> Rossen_: If it's not ready for resolution let's remove the agenda+ and continue moving forward<br>
</details>


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


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

Received on Wednesday, 5 April 2023 23:36:46 UTC