- From: François REMY <francois.remy.dev@outlook.com>
- Date: Mon, 18 Aug 2014 22:10:34 +0200
- To: "Peter Salas" <psalas@microsoft.com>, "CSS WG" <www-style@w3.org>
- Cc: "Tab Atkins" <jackalmage@gmail.com>
>> - If the track has a ‘max-content’ max track sizing function, set its >> growth limit to the maximum of the items’ max-content contributions. >> This is undefined, there is no such item (so I leave >> limit=infinity) >> -- I guess the difference between IE and me is here, it probably >> sets the limit to 0 at this step, why? > > Not quite; this is done after accommodating spanning items. > In the earlier version of the algorithm, this was the purpose of Step 4 > in ResolveContentBasedTrackSizingFunctions[1]. > > I don't see a place in the latest editor's draft algorithm where this > happens though. Ok, so this is probably something that may need to be improved in the new draft, because I didn't see any reference to it indeed. >> Therefore, how can we possibly get a limit of infinity in the following >> steps, which seem to take care of this possibility in multiple places? > > By "the following steps" were you referring to the "accommodate spanning > items" step? This is what I meant, indeed. > Does that answer your question? Yes, thank you.
Received on Monday, 18 August 2014 20:11:05 UTC