- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Sun, 19 Apr 2020 11:16:09 +0000
- To: public-css-archive@w3.org
> What could potentially be done is, at computed-value time, say that e.g. if `display-outside` computes to `table-cell`, then `display-inside` must compute to `flow-root` even if some other value was specified. Or maybe make both of them [invalid at computed-value time](https://drafts.csswg.org/css-variables-1/#invalid-at-computed-value-time) or something (there are various possibilities to prevent the combination at computed-value time, which one is better?). As @MatsPalmgren pointed out, `table-cell grid` shouldn't be a problem. In order to be able to introduce `display-outside`/`display-inside` properties, it needs to be clarified whether that applies to all combinations of `<display-outside>`/`<display-inside>` values, and if not, how to resolve those combinations. From a gut feeling, I'd say keeping the computed value of `display-outside` forcing the `display-inside` value is the way to go, as authors probably don't expect both to be invalidated in this case. Though I didn't give this much thought yet. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4729#issuecomment-616107064 using your GitHub account
Received on Sunday, 19 April 2020 11:16:12 UTC