Stanimir Stamenkov <[EMAIL PROTECTED]> wrote:
Frank Nospam wrote:
I still find Mozilla's rendering of this page completely bizarre: http://www.renewnyc.com/plan_des_dev/wtc_site/new_design_plans/ http://bugzilla.mozilla.org/show_bug.cgi?id=186942
Could you please make a test case out of this generated crap?
http://bugzilla.mozilla.org/attachment.cgi?id=116770&action=view
Validated HTML 4.01 and CSS2 for your enjoyment.
It is not my enjoyment, count on it - I just see hilarious "web design" decisions.
FYI, I'll break the issue in smaller pieces so we would get cleaner test case:
First off we see *absolutely* dimensioned DIV (a containing block) with some content larger than the dimensions specified. This is where your erroneous thinking begin - when you have _explicit_ dimensioned box its content doesn't cause it to resize but generates overflow which is controlled through the 'overflow' property <http://www.w3.org/TR/CSS21/visufx.html#overflow-clipping>.
On the other hand the content of the containing block box doesn't participate in the layout in which the containing block is placed. So we see exactly what it should be. For example the very first cell (top-left) of the table in your test case:
A 10x10 pixels box right aligned in the table cell. It has a content which overflow, just because the box has its size explicitly set but the content is bigger, but it doesn't affect the layout in which the containing box is placed. It is just shown outside the box ('overflow: visible').
The only thing I could think of erroneous rendering here may be is why the images are not shown overlapping the other cells in the table. But tables have been always subject to more restrictions and I'm not sure if there is something about that.
-- Stanimir <stanio(_at_)gbg.bg>
