Re: [csswg-drafts] [css-conditional] Element queries (#10509)

I wonder if there would be a path for adding something like @bkardell's `available-inline-space` keyword (see [All Them Switches](https://bkardell.com/blog/AllThemSwitches.html)) to the inline `if()` as a step in this direction? We could focus on the features needed for the inline solution, and then see if there's a good path to making it block-level as well?

@kizu You're suggesting that  de-sugared `if()` statements would already imply:

- The self-querying custom property becomes Invalid at Computed Value Time
- That variable bing queried in other properties would make them IACVT as well

That sounds reasonable to me, though I'm not sure if that's already part of `if()`. Does that proposal currently query the same element, or does it look at the parent?

I think it's probably good that your proposal would invalidate the entire block – so the rule block is all-or-nothing – but doing it at computed value time does seem rough unless we have something like `!revertable`. 

Other query types (like size queries) might be a bit more complicated? We would have to disallow changing anything that could impact size in any way – which isn't always a clear or concise restriction.


-- 
GitHub Notification of comment by mirisuzanne
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10509#issuecomment-2422822198 using your GitHub account


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

Received on Friday, 18 October 2024 16:18:05 UTC