- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Jul 2017 08:00:48 +0000
- To: public-css-archive@w3.org
Another thing: I initially described this as used value time on the display property, which was wrong because there isn't really such a thing, but the intent behind this attempt was:
* Hook into an existing mechanism (the flow-root logic of the display property) to avoid creating a similar but different thing
* Don't affect the computed value of the display property, because multicol (which uses this) never did, and other cases that turn things into (B)FCs (such as setting overflow to something other than visible, or the position property, or the float property) also don't affect the computed value of the display property
Regardless of what we do, I do not think that we should affect the computed value of the display property, as that would introduce a behavior change through inheritance. I don't expect that the following code is particularly common, but there's no reason to introduce a breaking change if we can avoid it:
```
.abs { position: absolute; }
.abs > div { display: inherit; }
```
This should not result in the nested div having a display flow-root.
Maybe we can just change this to "has the same effect as".
--
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-316304339 using your GitHub account
Received on Wednesday, 19 July 2017 08:00:54 UTC