[csswg-drafts] [css-conditional-5] Missing edits for queryless `@container` (#13674)

cdoublev has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-conditional-5] Missing edits for queryless `@container` ==
Omitting `<container-query>` in the prelude of `@container` is allowed since #9192.

But [§ 5. Container Queries](https://drafts.csswg.org/css-conditional-5/#container-queries) seem to be missing related edits:

  > By default, all elements are **query containers** for the purpose of container style queries, and can be established as query containers for container size queries and container scroll-state queries by specifying the additional query types using the `container-type` property (or the `container` shorthand). Style rules applying to a query container’s flat tree descendants can be conditioned by querying against it, using the `@container` conditional group rule.

I do not know if elements can be established as *query containers* if they match a `@container`'s condition whose `<container-query>` is omitted. Perhaps *query containers* should be reworded to *condition containers*?

---

<details>
<summary>Somewhat related. Browsers seem to match <code>&lt;container-name></code> against the <i>computed value</i> of <code>container-name</code>, as shown in this example.</summary>
<br>
```html
<style>
  article {
    --name: name;
    container-name: var(--name);
  }
  @container name (--name: name) {
    div { color: green }
  }
</style>
<article>
  <div>green</div>
</article>
```
</details>

Evaluating the computed value is explicitly defined for size/style/scroll container query, but not for the query container name. 

Could it be?

```diff
  The <container-name> filters the set of query containers considered 
- to just those with a matching query container name.
+ to just those with a matching specified value of their query container name.
```

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13674 using your GitHub account


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

Received on Wednesday, 18 March 2026 13:00:21 UTC