- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Jun 2018 19:33:30 +0000
- To: public-css-archive@w3.org
Overall, this seems like a change that somewhat simplifies your mental model of what goes on, but complicates the actual spec model due to its interaction with legacy compat requirements on how things must compute. (The FC-ification isn't reflected in any actual values; it just becomes something additional that's tossed onto the element due to it being blockified.) As @fantasai says, every place that blockifies currently also establishes an FC anyway, so we have no use-case for making blockification additionally imply FC-ification. Because of this, we also don't know if we would *want* to force that connection; there very well might be an example in the future where we want to blockify but lose the FC! The FC-ification part of every current spot is also a significant part of the spec that deserves calling out at the location, anyway, so we wouldn't even be saving ourselves any wordiness if we folded the behaviors together. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2673#issuecomment-395866160 using your GitHub account
Received on Friday, 8 June 2018 19:33:38 UTC