- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Apr 2022 20:52:06 +0000
- To: public-css-archive@w3.org
Copying my point from https://github.com/w3c/csswg-drafts/issues/7180#issuecomment-1082704210 over to here: Making all values of a shorthand optional is incorrect. As @tabatkins said on the call, you might use `[ ... ]!` to force a value to be set. Though this comes with some downsides. As @andruud already pointed out, the current definition allows values starting with a slash, which is probably not something you'd expect. And _if_ the slash is meant to go away when only one value is specified, container names can clash with the container type keywords. So, either we make the container name obligatory as @andruud wrote and which I support, or we allow to only specify a container type (without leading slash), and clarify in the prose that the container type keywords cannot be used as container names. Regarding the slash: This could either be solved via the syntax I suggested in the other issue, or by generally implicitly omitting slashes at the beginning or end of values. I actually tend to the latter option. Therefore I created #7200 now. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7142#issuecomment-1089332287 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 5 April 2022 20:52:08 UTC