[css-contain] Defer style queries to level 4?

[mirisuzanne]

We are much farther along with the development of (and experimentation with) size-based container queries. I want to make sure we have a plan from the start for how additional container/query types (like style queries) will be handled in the top-level syntax, but we could move the internal details of style-based queries into level 4, if it helps browsers more quickly get interop on the more established size features.

/cc @jensimmons who suggested this approach.

[fantasai]

I don't think there's a lot of internal details to sort out wrt style-based queries, so my take would be to just leave them in L3. And be clear that it's OK if browsers ship size queries in a release before they ship style queries.

[mirisuzanne]

Yeah, you might be right - at least for the basics of a direct property/value match. It seems like there will be interest in having the ability for more fuzzy matching at some point (checking for ranges on numbers, or contrast on colors, etc) – but I suppose we could delay those questions without delaying the entire feature.

[css-meeting-bot]

The CSS Working Group just discussed [css-contain] Defer style queries to level 4?, and agreed to the following:

• RESOLVED: Keep style queries in level 3.

The full IRC log of that discussion

<emeyer> Topic: [css-contain] Defer style queries to level 4?
<emeyer> Github: https://github.com//issues/7020
<emeyer> miriam: Jen Simmons raised this to me, so I posted it here. Elika and I feel that the spec as it is is direct and simple, not a lot of questions. We might as well ship it with the rest of the spec. If there are implementor concerns, we can hold it back.
<emeyer> Rossen: Miriam, which do you want?
<emeyer> miriam: Let’s keep it in L3 since it’s already defined.
<emeyer> Rossen: Any objections?
<emeyer> (silence)
<emeyer> RESOLVED: Keep style queries in level 3.
<emeyer> topicend