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

Re: Insufficient margins/padding for list-items/quotes/etc. next to ?floats

From: James Hopkins <james@idreamincode.co.uk>
Date: Sun, 27 Dec 2009 01:28:51 +0000
Cc: www-style@w3.org, Aryeh Gregor <Simetrical+w3c@gmail.com>
Message-Id: <F2E531BE-43C0-4D07-9313-D4E113968D38@idreamincode.co.uk>
To: L. David Baron <dbaron@dbaron.org>
>> My initial thought is a new property, inherited, like (names not
>> remotely serious)
>> extra-float-spacing: none | new-behavior
>> "none" would give the current behavior.  "new-behavior" would behave
>> something like this.  Suppose we have a line box L that would overrun
>> a float F.  Let E be the most distant ancestor of L that is not an
>> ancestor of F.  When shrinking L, leave an extra amount of space  
>> equal
>> to the space you would get if E established a new block formatting
>> context, plus the margin of E (subject to margin collapsing).  As
>> usual, if the line box can no longer fit, it gets pushed down.  I'm
>> being lazy here in saying how much space should actually be left --
>> the idea is all the margins and padding of E and its descendants
>> containing L, but with margin collapsing and other magic working as
>> usual.

Ah, I see the use case for such a mechanism now.

> There was actually a proposal for this in old drafts of css3-box:
> http://www.w3.org/TR/2002/WD-css3-box-20021024/#the-float-displace
> (See also my comments on it in
> http://lists.w3.org/Archives/Public/www-style/2008Feb/thread.html#msg116 
>  .)

My immediate question is why the 'float-displace' proposal was dropped  
in the first place. I notice you asked this in your initial email (http://lists.w3.org/Archives/Public/www-style/2008Feb/0116.html 
), however, I also see there was no reply. 
Received on Sunday, 27 December 2009 01:29:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:41 UTC