- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Sep 2022 23:14:33 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-contain-3] .conditionText and name vs query`, and agreed to the following: * `RESOLVED: Add .containerName and .containerQuery` <details><summary>The full IRC log of that discussion</summary> <fantasai> Subtopic: [css-contain-3] .conditionText and name vs query<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/7190<br> <fantasai> miriam: Currently we have .conditionText which is a single string<br> <fantasai> miriam: but includes 2 parts, a name for name of container and a query for the conditions to match against that container<br> <fantasai> miriam: so proposal is to keep .conditionText as the entire query<br> <fantasai> miriam: but add .containerName and .containerQuery so you can get the parts yourself<br> <fantasai> astearns: if we have the parts, why do we need the concatenated thing?<br> <fantasai> TabAtkins: to match the other conditional rules<br> <fantasai> heycam: it inherits from ConditionalRule, so need to say what that property returns<br> <fantasai> astearns: Anyone with opinions?<br> <TabAtkins> +1<br> <fantasai> +1 from fantasai<br> <fantasai> heycam: makes sense to me<br> <TabAtkins> (and emilio already implemented it, apparently)<br> <fantasai> heycam: just question, the one that returns the expression<br> <fantasai> heycam: that doesn't include the parentheses?<br> <fantasai> miriam: that would include potentially multiple expressions<br> <fantasai> heycam: was asking about outermost parens<br> <fantasai> miriam: they're not required<br> <fantasai> miriam: no need to include them there<br> <fantasai> heycam: ah, so parens are part of the expression, not extra syntax<br> <fantasai> miriam: right<br> <fantasai> astearns: objections?<br> <fantasai> miriam: @andruud already posted a PR, so we could resolve to merge the PR<br> <fantasai> astearns: Not seeing anything about parens<br> <fantasai> miriam: if they are included, not part of the .containerQuery?<br> <fantasai> astearns: need to know whether to expect the parens<br> <fantasai> miriam: could merge the PR and add that as well<br> <astearns> ack fantasai<br> <heycam> fantasai: the syntax is like for MQs<br> <heycam> fantasai: so there are potentially a redundant set of parens around the entire expression, but in lots of cases you'll have ( expr ) or ( expr )...<br> <heycam> fantasai: any parens there should appear there<br> <heycam> fantasai: if we want to simplify, we should do it all the way through<br> <fantasai> heycam: I guess I wasn't suggesting simplification<br> <fantasai> heycam: wasn't sure if outermost parens were part of @container rule syntax<br> <fantasai> heycam: but sounds like it's part of the expression<br> <fantasai> astearns: so it's just as specified, with whatever parens<br> <fantasai> miriam: yes<br> <fantasai> astearns: then we can resolve to accept this PR and add these attributes<br> <fantasai> RESOLVED: Add .containerName and .containerQuery<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7190#issuecomment-1240008814 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 September 2022 23:14:35 UTC