- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Sep 2020 22:01:24 +0000
- To: public-css-archive@w3.org
Hmm. So, the shortcut values don't do anything that's not expressible by just writing some of the longhands. So shortest-serialization would normally imply that a specified `contain: layout paint;` should serialize as `contain: content;`. However, in <https://github.com/w3c/csswg-drafts/issues/5506#issuecomment-692724381> Oriol points out that if we introduce more shorthands that no longer form a strict hierarchy (currently they do), we'll have to deal with ambiguous shortest serializations. Not necessarily a problem, we can just spec our way out of it if necessary. I'm inclined to specify that the computed value is the set of containments being applied, and they serialize using SSP. That would allow the internal impl to be a bitfield, which is reasonable, and I don't anticipate ever adding something that wouldn't be part of that. I'm happy to specify the application of SSP more specifically, too, to make sure that this is utterly clear. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5511#issuecomment-693002908 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 15 September 2020 22:01:26 UTC