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

RE: [css3-exclusions] inline layout and wrap-flow:both

From: Rossen Atanassov <Rossen.Atanassov@microsoft.com>
Date: Wed, 30 May 2012 16:36:20 +0000
To: "robert@ocallahan.org" <robert@ocallahan.org>, www-style <www-style@w3.org>
Message-ID: <9A57384B9CE9AE4F9C01F3BB5C3D8844014FEE1D@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
> -----Original Message-----
> From: rocallahan@gmail.com [mailto:rocallahan@gmail.com] On Behalf Of
> Robert O'Callahan
> Sent: Monday, May 21, 2012 5:58 PM
> 
> The spec doesn't seem to say anything about how inline formatting works when
> an exclusion divides a line into multiple discontiguous segments of available
> space in the inline progression direction. This could never happen in CSS before.

Correct, floaters only restrict the space of inline content but never split it. If we haven't already I will open an issue to add a section about this. 

> It seems to me that quite a few issues will need to be sorted out. For example,
> example 1 in the draft shows hyphenation and justification being applied to each
> segment individually. This needs to be specified. If the idea is to treat each
> segment as a different line, that needs to be specified. 

Right, the approach is to treat each empty segment and the inline content that falls into separately for the purposes of inline layout. This means that alignment in the character direction is done per line segment while alignment in the block progression is done considering the baselines.

> You would need to specify whether ::first-line applies to the first segment of a line or the whole
> line. You would need to clarify how text-indent works if the text-indent is wider
> than the first segment. Etc.

Sure, these are valid topics that should be mentioned.

Thanks,
Rossen
Received on Wednesday, 30 May 2012 16:38:01 GMT

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