W3C home > Mailing lists > Public > www-style@w3.org > April 2013

Re: [css-multicol] Overflowing floats issue

From: Robert O'Callahan <robert@ocallahan.org>
Date: Mon, 29 Apr 2013 22:50:31 +1200
Message-ID: <CAOp6jLYYx4YE0HUn9NGx0Zu+n04G1A2dd0qA7tbpMsUaM8h8mg@mail.gmail.com>
To: François REMY <francois.remy.dev@outlook.com>
Cc: "www-style@w3.org" <www-style@w3.org>
On Sun, Apr 28, 2013 at 8:11 AM, François REMY <
francois.remy.dev@outlook.com> wrote:

> Halas, the rendering I would like to see is to be seen in none of the
> considered browsers (but IE's rendering would satisfy me; the webkit
> rendering is clearly an artifact of their "one flow, multiple clipped
> rendering" implementation). Just for the record, I would prefer the image
> to be sent to the next page and none of text after the img tag to be
> rendered on the first column. The reason I want this is to make sure I can
> draw a logical DOM split between the columns. If the image is sent to the
> next column, I think no text that follows the image should be visible in
> the column.
>
> Any comments?
>

In Gecko we deliberately do what you don't want --- pull content from after
the float before the float, when we've moved the float to the next column.
If we do it your way, you can end up with a lot of wasted space.

Maybe there's an argument for providing a switch to let authors control
whether this is allowed.

Rob
-- 
q“qIqfq qyqoquq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qyqoquq,q qwqhqaqtq
qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq
qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qtqhqeqmq.q qAqnqdq qiqfq qyqoquq
qdqoq qgqoqoqdq qtqoq qtqhqoqsqeq qwqhqoq qaqrqeq qgqoqoqdq qtqoq qyqoquq,q
qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq
qsqiqnqnqeqrqsq qdqoq qtqhqaqtq.q"
Received on Monday, 29 April 2013 10:51:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 April 2013 10:51:03 UTC