Suggest split Container Style Queries into custom properties and standard properties

[woody-li]

The first standard of Container Style Queries is CSS Containment 3.
But there's some questions for standard properties usage: w3c/csswg-drafts#7185

Chrome implementd it only for custom properties.
Webkit expressed support position fot custom properties: WebKit/standards-positions#57
MDN data only shows the custom properties usage.

So is it necessary to split it into the two pages?

[jensimmons]

I'm not sure that Style Queries for standard properties will ever happen. It's likely it will not.

[SebastianZ]

I'm not sure that Style Queries for standard properties will ever happen. It's likely it will not.

The resolution from last week indicates that they'll be added to level 4.

Anyway, in regard of the resolution, I suggest to just change the feature title and description to note that they only apply to custom properties for now.
I.e. change the title to "CSS Container Style Queries for custom properties" and the description to "Style queries in Container Queries provide a way to query the current styling defined in custom properties of a container, and conditionally apply additional CSS to the contents of that container."

Once Style Queries for standard properties become a thing, a new entry can be added to cover them.

Sebastian

[woody-li]

What's more, Safari 18 will support it: https://developer.apple.com/documentation/safari-release-notes/safari-18-release-notes#CSS

[jensimmons]

Yes, Safari 18 beta supports CSS Container Style Queries for custom properties. We are supportive of the idea of making that page its own feature, since support for all properties is separate in the specification.

[mirisuzanne]

For the foreseeable future, style queries will be only for custom properties in all browsers. I do think non-custom property queries should be treated as a distinct feature, currently with no support. And the browsers that support custom property queries should show full support for that feature. Since the browsers are treating these as distinct features, authors are as well, and support data should reflect that.