W3C home > Mailing lists > Public > www-style@w3.org > April 2016

[css-grid] Should we re-run the sizing algo on max-content size changes, too?

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 11 Apr 2016 13:11:03 -0700
Message-ID: <CAAWBYDA24qyzpVmYn+kEdJ1J5TD4r0+j2rjTOqbE=aMR-T8woA@mail.gmail.com>
To: www-style list <www-style@w3.org>
Cc: Rossen Atanassov <Rossen.Atanassov@microsoft.com>, Peter Salas <psalas@microsoft.com>
This is about Grid DoC Issue 20
<https://drafts.csswg.org/css-grid/issues-wd-20150917#issue-20>.

Currently, step 3 of the Grid Sizing Overview
<https://drafts.csswg.org/css-grid/#algo-overview> requires that you
rerun the sizing algorithm once if any of the grid items had their
min-content contribution changed due to Step 2.  This catches things
where their inline size depends on the available space in the block
dimensions, such as column-wrap flexboxes, or orthogonal flows, and
gives them a chance to stabilize to a "correct" size.  (Theoretically
this is iterate-until-stable layout, but apparently it's good enough
to just do it twice, at least according to MS's initial
implementation.)

This step has been present since the original Microsoft algorithm
<https://www.w3.org/TR/2013/WD-css3-grid-layout-20130402/#layout-algorithm>,
and it's always been solely about changing min-content contributions.
But what about max-content contributions?  Some parts of the algo do
care about max-content, and it seems like that would have a similar
set of problems if we didn't adjust for it.

Can anyone think of a good reason why that step only fires on
min-content contribution changes, and not max-content?  If not, does
anyone object to us making it fire on max-content contribution changes
as well?

~TJ
Received on Monday, 11 April 2016 20:11:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:02 UTC