- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Mon, 10 Dec 2012 10:09:06 -0800
- To: Rossen Atanassov <Rossen.Atanassov@microsoft.com>
- Cc: Ojan Vafai <ojan@chromium.org>, Rudolph Gottesheim <r.gottesheim@loot.at>, Morten Stenshorne <mstensho@opera.com>, "www-style@w3.org" <www-style@w3.org>
On Sun, Dec 9, 2012 at 5:09 PM, Rossen Atanassov <Rossen.Atanassov@microsoft.com> wrote: >> Okay, based on this thread and the existing browser behavior, we've clarified >> step 11 in the layout algo to say that it looks at the >> *computed* value of the cross-size property to tell whether it can stretch or >> not. Based on the errata mentioned in this thread, that means that >> percentages which later turn into auto behavior won't get stretched. >> >> If someone feels strongly that we should instead be using used-value-time >> auto (which is theoretically possible, since this is happening in the middle of >> layout), speak up! > > What was the reason to refer to the computed instead of used value here, perf? I'm not sure if it's better perf or not, but it's simpler unless there's a good reason to do otherwise. > I am more interested to see behavior where flex items don't overlap, so let's try to work on that. ? This has nothing to do with flex items overlapping (note that it's about the cross-axis). ~TJ
Received on Monday, 10 December 2012 18:09:55 UTC