W3C home > Mailing lists > Public > www-style@w3.org > February 2012

RE: [css3-regions][css3-gcpm] Plan B versus Plan A

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Mon, 6 Feb 2012 15:52:07 +0000
To: Håkon Wium Lie <howcome@opera.com>, Alan Stearns <stearns@adobe.com>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <D51C9E849DDD0D4EA38C2E539856928412E45E7C@TK5EX14MBXC214.redmond.corp.microsoft.com>
> From: Håkon Wium Lie [mailto:howcome@opera.com]
> Sent: Monday, February 06, 2012 4:11 PM
> 
> This is also a problem in the first example of the Regions draft:
> 
>   http://www.w3.org/TR/2011/WD-css3-gcpm-20111129/regions.png
> 
> By setting the height of region 1 in ems, pixels, or percentages, one risks
> unintentionally blank lines.
> 
> An alternative is to select lines directly. For example:
> 
>   article { columns: 3 }
>   img, p.lead::first-lines(3) {
>     column-span: 2;
>   }

This example assumes that first-line pseudoelement can take block properties (such as 'column-span') which is highly speculative.

If a new feature is needed to support that kind of sizing, having a "line-height" unit would work better:

	#region2 { height: 4li; }

(same is important for good quality drop caps BTW).

"line-height" unit can be complicated when font size varies in line, but it works very well for typical designs that want to emphasize first few lines of content. 
Received on Monday, 6 February 2012 15:52:52 GMT

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