- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Oct 2021 22:53:11 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-contain-3] Define a syntax for style-based container queries`, and agreed to the following: * `RESOLVED: Accept proposal in ED. Split range syntax and attributes to new issue` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-contain-3] Define a syntax for style-based container queries<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/6396<br> <fantasai> i/Topic/astearns: Resolved, unless someone comes back with a strong opinion later<br> <dael> miriam: style based container queries are idea we can look at container and check computed value of a property and query that and change things for desc for value of property<br> <dael> miriam: Mostly used for high level custom prop where have set of values, check on parent, and based on query make changes<br> <dael> miriam: Other use cases, that's main<br> <dael> miriam: fantasai and I added proposed syntax to spec.<br> <dael> miriam: At this point it uses normal property syntax so : between. Some issues about supporting range syntax or attribute selector syntax<br> <dael> astearns: Opinions?<br> <dael> TabAtkins: Defining equality as something we haven't done in css. Will require some work. Wait, we have equality for transition. Ignore me. On to fantasai<br> <astearns> ack fantasai<br> <astearns> s/TabAtkins.*$//<br> <dael> fantasai: We talked about potentially having range. Was hesitant b/c if want to catch range of values for width you would not be able to do with style query b/c can only compare length but not auto or other keyword-based width values<br> <smfr> q+<br> <dael> fantasai: Reason I didn't want to add range syntax for computed style is b/c will add confusion. Some point in future may have use cases to add but best for now to keep to equal or not<br> <astearns> ack smfr<br> <dael> fantasai: Mostly will do lengths and use container queries for things with sizes<br> <dael> smfr: A bit confused. Understood container queries limited to elements with certain values on contain property.<br> <dael> smfr: Feature here sounds like could be independant of contain property. Features here apply whe not using?<br> <dael> miriam: Resolved earlier to use sytax to establish containers. Then browser establishes containement behind the scenes. This would rely on container type that doesn't apply containment in background<br> <dael> smfr: Makes sense<br> <dael> astearns: Other comments?<br> <dael> astearns: My understanding is we're looking for resolution to accept what's in ED and leave range syntax and attributes to future issues<br> <dael> miriam: wfm<br> <dael> astearns: fremy it was your comment about attributes. Okay to ask you to open new issue?<br> <dael> fremy: Isn't it same issue but delay to new level? I can open a new one if people prefer<br> <dael> fantasai: Yes please<br> <fremy> fantasai: ok, will do<br> <dael> astearns: Prop: Accept proposal in ED. Split range syntax and attributes to new issue<br> <dael> RESOLVED: Accept proposal in ED. Split range syntax and attributes to new issue<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6396#issuecomment-937299667 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 October 2021 22:53:12 UTC