- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Mar 2022 17:31:36 +0000
- To: public-css-archive@w3.org
Yes, sorry, the spec (and tests) are out-of-date with the current resolutions (because I thought we were revisiting a decision, but then we didn't). I'll get those changes in the spec today/tomorrow. Sorry for the confusion. In brief: - [We resolved](https://github.com/w3c/csswg-drafts/issues/6393#issuecomment-1011283604) that the initial value of container-type is `style`, not `none`. - In the same resolution, since both name & type are now 'optional' for a container, we swapped the order of the `container` shorthand to encourage naming containers. - (we also swapped the order in `@container` so they would match, but then [we removed `container-type`](https://github.com/w3c/csswg-drafts/issues/6393#issuecomment-1034059934) from that syntax altogether) So, in relation to the shorthand syntax that means currently: - If no container-name is provided, it is set to `none` (#7142 suggests making this explicitly required) - If no container-type is provided, it is set to `style` -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7180#issuecomment-1083422839 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 March 2022 17:31:38 UTC