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

[csswg-drafts] [css-grid] Collapsed grid tracks and content distribution

From: SelenIT via GitHub <sysbot+gh@w3.org>
Date: Wed, 29 Mar 2017 10:35:19 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-217833549-1490783718-sysbot+gh@w3.org>
SelenIT has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-grid] Collapsed grid tracks and content distribution ==
According to the CSS Grid spec, the grid tracks that [collapse](https://drafts.csswg.org/css-grid/#collapsed-track) because of `auto-fit` repetition, have zero width and the gutters between them also [collapse](https://drafts.csswg.org/css-grid/#collapsed-gutter):
> When a collapsed track’s gutters collapse, they coincide exactly—the two gutters overlap so that their start and end edges coincide. If one side of a collapsed track does not have a gutter (e.g. if it is the first or last track of the implicit grid), then collapsing its gutters results in no gutter on either “side” of the collapsed track.

The question is, how these collapsed tracks and gutters should be treated for the `justify-/align-content` purposes? On the one hand, the collapsed tracks are still technically separate tracks, so they may be distributed as usually (which we currently see in Blink/WebKit implementation). On the other hand, "the exact coincidence" of the collapsed grid gutters, one of which is the last track gutter, seems to imply that there would be effectively no gutter after the last non-empty track, so no extra space to distribute, and the non-empty tracks should be distributes as if the collapsed tracks didn't exist at all. This is what currently the Gecko implementation does.

The difference in the two implementations behavior can be seen in this example (provided by @mrego): http://jsbin.com/rosarub/edit?html,css,output

Persolally, I believe that the Firefox's behavior (ignoring the collapsed tracks completely) makes more sense from the practical perspective. Having invisible things that affect distribution of the visible content is confusing and sometimes even annoying, the same way as [wrapping abspos children of the flex container in anonymous flex items](https://bugzilla.mozilla.org/show_bug.cgi?id=1269045) was. I supposed that that the whole point of collapsing tracks is making them not affecting the layout at all. But it's just my opinion.

Should the spec be clarified for this aspect?

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1140 using your GitHub account
Received on Wednesday, 29 March 2017 10:35:28 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:09 UTC