- From: SelenIT via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Jan 2017 16:32:06 +0000
- To: public-css-archive@w3.org
There is a problem with "flow-block" suggestion: there is already a `display: block flow` [longhand value](https://drafts.csswg.org/css-display/#display-value-summary) in the spec, which means _just the opposite_ — the block that _doesn't_ establish new block formatting context (i.e., default `display:block` behavior). Would be way more confusing that the current naming. If I understand correctly, the whole flow/flow-root thing that @fantasai explains in https://github.com/w3c/csswg-drafts/issues/964#issuecomment-274638719 applies only to blocks and inlines (collectively referred as "flow layout") since they are the only two display values that can have the same formatting context inside as outside. It doesn't make sense for flex and grid containers since they always establish the new formatting context (different from the one they live in themselves) and therefore don't have issues like float leaking or descendant margin collapsing. But I like the idea to have a separate property for switching new context generation on/off. Maybe this behavior has something to do with the scope of [css-containment], especially with [`contain:layout`](https://drafts.csswg.org/css-containment/#containment-layout)? Looks like something very similar from the first glimpse, and new formatting context is explicitly mentioned there. -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/964#issuecomment-275431659 using your GitHub account
Received on Thursday, 26 January 2017 16:32:15 UTC