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

Re: padding lost in overflow

From: Alan Gresley <alan@css-class.com>
Date: Sat, 11 Jan 2014 17:11:06 +1100
Message-ID: <52D0E07A.70502@css-class.com>
To: Brad Kemper <brad.kemper@gmail.com>, "Tab Atkins Jr." <jackalmage@gmail.com>
CC: Mats Palmgren <mats@mozilla.com>, Ojan Vafai <ojan@chromium.org>, "www-style@w3.org" <www-style@w3.org>, David Baron <dbaron@dbaron.org>, Daniel Holbert <dholbert@mozilla.com>, Elliott Sprehn <esprehn@chromium.org>
On 11/01/2014 9:59 AM, Brad Kemper wrote:
>
>
>> On Jan 10, 2014, at 2:24 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:
>>
>> It seems more logical to lay out the contents normally, as if you were
>> doing overflow:visible, then grow the content box to fully contain the
>> contents, and wrap the padding box around that as normal.  The first
>> part is what we do already; it's really weird that the content box is
>> allowed to overflow the padding box.
>
> I completely agree.

Tab, for the content box to fully contain the contents, this also 
requires that there is no clipping of the content's margin-box. This is 
how IE7 rendered overflowing content with overflow:scroll. This was 
raised as an issue by Bruno Fassino in February 2008 in this thread [1] 
titled 'Overflow and Margins" and is also a very old gecko bug [2].

There is also the CSS3 overflow [3] that I had hoped would eventually 
define overflow. Whatever is decided, it would make sense to have the 
same behavior for the root element or viewport.


1. http://lists.w3.org/Archives/Public/www-style/2008Feb/thread.html#msg0
2. https://bugzilla.mozilla.org/show_bug.cgi?id=47710
3. http://wiki.csswg.org/spec/css3-overflow


Alan


-- 
Alan Gresley
http://css-3d.org/
http://css-class.com/
Received on Saturday, 11 January 2014 06:11:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:38 UTC