W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2017

Re: [csswg-drafts] [css-align][css-multicol] 'justify-content' other than 'normal' or 'stretch' should change column count/size rules

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Tue, 27 Jun 2017 18:50:36 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-311450694-1498589435-sysbot+gh@w3.org>
> Hmmm. Grid gaps were designed to be the same as grid tracks, except empty, so I expect that behavior on Grid. Column gaps were not, so I do not have the same expectation.

Right, thus the "slightly unfortunate implications" note.  I agree it's slightly worse behavior, but when weighed against a strong inconsistency with how gaps work elsewhere, I think it's better for the future for column-gap to be consistent between Multicol and Grid. Special cases make people sad.

> Yeah, but the default value of column-gap is normal, not a specific length, so to use that approach you can no longer rely on the default value of column-gap.

Correct (but in practice it's 1em, you can just use that).

> to preserve the current behavior of "single column multi-col is indistinguishable form block layout in a BFC"?

We already have that behavior - if `justify-content` is `normal` or `stretch`, a 1-column multicol continues to act exactly like Block. If it's anything else it doesn't, but Block doesn't pay attention to `justify-content` at all, so it's the *author* breaking the symmetry, not the spec.  (Block doesn't have a notion of "content width" separately from "box width" like multicol does.)  There's no need to do anything extra-special to try and maintain the linkage past where it makes sense.

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1420#issuecomment-311450694 using your GitHub account
Received on Tuesday, 27 June 2017 18:50:43 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:30:34 UTC