- From: Guillaume via GitHub <noreply@w3.org>
- Date: Mon, 30 Mar 2026 12:43:30 +0000
- To: public-css-archive@w3.org
cdoublev has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-conditional-5] Consider deprecating and removing `CSSContainerRule.containerName` and `CSSContainerRule.containerQuery` == In #10845, the CSSWG resolved on adding [`CSSContainerRule.conditions`](https://drafts.csswg.org/css-conditional-5/#dom-csscontainerrule-conditions) to represent the list of `@container` conditions, and to make `CSSContainerRule.containerName` and `CSSContainerRule.containerQuery`, which were defined before changing the grammar to accept more than one name, return the empty string if the list has more than one condition. This change was made with the following note: > [!CAUTION] > We should try to remove `containerName` and `containerQuery`, since they don’t deal with multiple conditions correctly. @emilio, who asked me to create this issue, added use counters to check if back-compat allows this. In my opinion, deprecating them could also be an appropriate action to consider. Returning empty string when there is more than one name/query shows that they are half broken. This would also send a signal (eg. via [MDN](https://developer.mozilla.org/en-US/docs/Web/API/CSSContainerRule)) to not use them, so that they can be removed. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13743 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 30 March 2026 12:43:31 UTC