W3C home > Mailing lists > Public > www-style@w3.org > June 2011

Re: region intrinsic size and aspect ratio

From: Brad Kemper <brad.kemper@gmail.com>
Date: Tue, 28 Jun 2011 12:41:49 -0700
Message-Id: <C7341B07-A261-4533-B7C9-044A9C6D908A@gmail.com>
Cc: "www-style@w3.org" <www-style@w3.org>, Edward O'Connor <eoconnor@apple.com>, Alex Mogilevsky <alexmog@microsoft.com>, "David Hyatt (hyatt@apple.com)" <hyatt@apple.com>
To: Vincent Hardy <vhardy@adobe.com>
On Jun 28, 2011, at 9:43 AM, Vincent Hardy <vhardy@adobe.com> wrote:

> c. Reconsider model and determine if we need a new model to compute the region's auto width/height
> 
> The model for regions is that formatting should be equivalent to having the content segments defined in the respective regions they fall into. So:
> 
> #article {
>     flow: into(article_flow);
> }
> 
> #region_1, #region_2 {
>     content: from(article_flow);
> }
> 
> <div id="article"><span id="fits_in_region_1">...</span><span id="fits_in_region_2">...</span></div>
> <div id="region_1"></div>
> <div id="region_2"></div>
> 
> should produce the same visual formatting as:
> 
> <div id="region_1"><span id="fits_in_region_1"></span></div>
> <div id="region_2"><span id="fits_in_region_2"></span></div>
> 
> In terms of processing, when formatting each region in turn, it is as if we were trying to fit in the remainder of the flow in each region. So to layout 'region_1', you proceed as if it had all of the flow content as a child. That will only consume 'fits_in_region_1' though. Then, to layout 'region_2', you proceed as if it had the remainder of the flow. 
> 
> pro: The advantage of this approach is that it does not introduce any new special specification for region sizing.

This option C seems very reasonable and intuitive to me. To get a max-intrinsic width on the region, I can just make it display:inline-block, or display-table-cell, no? 
Received on Tuesday, 28 June 2011 19:42:24 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:41 GMT