- From: Rune Lillesveen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 Jun 2022 11:28:23 +0000
- To: public-css-archive@w3.org
It's not clear to me how container-type should be split into different longhands.
If we split into separate longhands, we would still have the issue with the container shorthand?
Say we have a new 'state' container type and split into size-container and state-container properties.
Setting both name and inline-size via the shorthand will reset the state-container:
```
#container {
state-container: foo
}
#container {
container: name / inline-size
}
```
If we add:
```
size-container: (none | inline-size | size)
```
Do we want to have a short-hand for setting size-container + container-name?
That is:
```
size-container-type: (none | inline-size | size)
size-container: name / size-container-type
```
Also, would that mean that we would not longer need the full container shorthand. Still an issue with a shorthand with:
```
size-container: size-name / inline-size
state-container: state-name / foo
```
if the first value is container-name
--
GitHub Notification of comment by lilles
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7066#issuecomment-1153800335 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 13 June 2022 11:28:25 UTC