W3C home > Mailing lists > Public > www-style@w3.org > January 2009

RE: [css3-gcpm] containing block for top/bottom floats

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Thu, 8 Jan 2009 11:23:43 -0800
To: Håkon Wium Lie <howcome@opera.com>, MURAKAMI Shinyu <murakami@antenna.co.jp>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <7C2F64B551D8664AAD94A28DAC37D0206B565ADD4F@NA-EXMSG-C103.redmond.corp.microsoft.com>

I don't think this works with nested blocks. If there is a block with left padding inside a column and that block contains a left float, the float will align with content box of the block, not the column.

It makes sense to say this for vertical floats (and perhaps column floats), but it has to be made clear that it doesn't apply to "regular" floats.

-----Original Message-----
From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf Of Håkon Wium Lie
Sent: Thursday, January 08, 2009 11:16 AM
Cc: www-style@w3.org
Subject: Re: [css3-gcpm] containing block for top/bottom floats

Also sprach MURAKAMI Shinyu:

 > What about the containing block for top/bottom floats when neither page
 > nor multi-column keyword is specified?

 > I expect the top-float is floated to the top of the current column.
 > But that is not obvious in the GCPM spec.

I have a new proposed solution for this.

First, the multicol spec will say that:

  Column boxes are containing blocks for content that appear inside them.

Then, GCPM will say:

        Indicates that the page box is the containing block for the element.
        Indicates that the multicol element is the containing block for the element.

And, in an example say:

  The column box is the containing block for floats, so if an image
  naturally appears in the first column it will float to its bottom:

This way, we avoid duplicating normative text and still say things
clearly. Does this address the issue adequately?

              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Thursday, 8 January 2009 19:24:56 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:23 UTC