You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then, other specifications that require blockifications (like flexbox or grid) wouldn't need to explicitly require a new formatting context, because it would already be implied.
Additionally, a flow-root inner display type becomes flow when blockified. Then someone could think that the element stops being a BFC root. Explicitly saying that this is not the case (because the element establishes a new formatting context) would clear up the confusion.
The text was updated successfully, but these errors were encountered:
Nope, grid items get blockified, but subgrids do not establish a new FC.
It's definitely usually the case (and could probably use a note in the spec that you can generally expect it), but it's not fundamental to blockification.
(The Grid 2 spec doesn't explicitly specify that subgrids don't form a new FC yet, but that's definitely what happens - their layouts intertwine with their parent, which is the definition of "not a new formatting context". We'll fix this in Grid 2 in a bit.)
It seems that in all cases in which an element is blockified, it also needs to establish a new formatting context.
So instead of specifying both transformations everywhere, it would be simpler if https://drafts.csswg.org/css-display-3/#transformations said that blockifying causes the element to establish a new formatting context.
Then, other specifications that require blockifications (like flexbox or grid) wouldn't need to explicitly require a new formatting context, because it would already be implied.
Additionally, a
flow-root
inner display type becomesflow
when blockified. Then someone could think that the element stops being a BFC root. Explicitly saying that this is not the case (because the element establishes a new formatting context) would clear up the confusion.The text was updated successfully, but these errors were encountered: