- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Fri, 18 Sep 2015 18:02:31 -0400
- To: Sergio Villar Senin <svillar@igalia.com>, www-style@w3.org
On 09/18/2015 08:31 AM, Sergio Villar Senin wrote: > Hi, > > I'd kindly ask the editors to clarify what being sized under min|max-content constraint exactly means[1] for the track sizing > algorithm. In particular I'd like to know if we're talking about just the width|height of the grid container or if we should > take a look also to our ancestors to check that (provided the grid has relative or auto sizes). > > Should we want to extend it to our ancestors then the implementations might start to suffer from severe performance issues > because we might need some extra layouts. For example if we want to take into account the values of min|max-width|height > restrictions then we need to layout to know whether we're we satisfy or not those conditions. It means when you're calculating the min-content/max-content contribution of the grid container, e.g. if the grid container happens to be inside a float (or is itself a float). ~fantasai
Received on Friday, 18 September 2015 22:03:02 UTC