- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Dec 2023 17:09:46 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-contain-3] Inconsistent handling of known and unknown features jeopardizes backward compatibility`, and agreed to the following: * `RESOLVED: No container is valid for unknown queries` * `RESOLVED: Add the comma-separated syntax.` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> miriam: In CQ resolving process, first step is finding the container taht can answer the questions<br> <TabAtkins> miriam: Then we query it<br> <TabAtkins> miriam: Issue we created here is that, right now, if we have an unknown condition in our query, we assume any container can answer it<br> <TabAtkins> miriam: Really should be that *no* container can answer it<br> <TabAtkins> miriam: down the road, when the unknown is supported, it should actually become conditional<br> <TabAtkins> miriam: If it's becoming true now, because we ignored it, that'll break if it's sometimes false later<br> <TabAtkins> miriam: Better to have it always false now, and then sometimes true later<br> <TabAtkins> miriam: Stalled due to some concern about backcompat. Rune did a use counter and found usage is extremely low<br> <TabAtkins> miriam: So hoping we can make the change despite it being breaking<br> <TabAtkins> miriam: First change - no container is valid for unknown queries (<general-enclosed>)<br> <TabAtkins> miriam: Second - add a comma-separated syntax so you can execute multiple queries that can match against multiple queries<br> <TabAtkins> miriam: The difference between logical "or" and a comma is the comma allows two different containers to be queried, while "or" is looking for a single container that can answer both questions<br> <TabAtkins> +1<br> <TabAtkins> astearns: Does the syntax have logical or currently?<br> <TabAtkins> miriam: I believe so (i'd have to double check)<br> <TabAtkins> astearns: So the comma-separated container-or could be combined with query-or<br> <TabAtkins> miriam: Yes, confirmed, logical "or" is allowed in spec currently.<br> <TabAtkins> astearns: Comments or concerns?<br> <TabAtkins> astearns: So let's resolve on the first<br> <TabAtkins> RESOLVED: No container is valid for unknown queries<br> <TabAtkins> astearns: Second is to add the comma-separated syntax, an "or" but allowing different containers<br> <TabAtkins> +1<br> <TabAtkins> RESOLVED: Add the comma-separated syntax.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7551#issuecomment-1854385652 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 December 2023 17:09:48 UTC