206436 - <div> with <table> unexpectedly cropped

Status: RESOLVED FIXED

(Core :: Layout: Tables, defect, P3)

Description

[Henrik Eriksson]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4b) Gecko/20030507
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4b) Gecko/20030507

On the URL above a list of songs gets cut in half. If you view the page source
you can see that the list is a lot longer than what actually gets rendered.

I've verified this bug on PC - Moz 1.3, MacOS X - Moz 1.4b. However on Mac - Moz
1.2.1 the page renders fine. Which makes me believe this is a regression. It
might be related to bug 197163 which seems to have regressed at the same time.

Though the source isn't the prettiest around it has rendered correctly in
Mozilla. Obviously it renders correctly in IE.

Reproducible: Always

Steps to Reproduce:
1. Go to URL above

Actual Results:  
List of songs cut in half even with a larger browser-window

Expected Results:  
Rendered the whole list and then render the page footer as it has done previously.

Comment 1

[Chris Casciano]

Initial glance this looks like an overflow issue. not sure if its specific to
tables or not.

it looks like div#divMainLeftCol has a set height of 570px. the table being
"cropped" is inside of this div. but that doesn't seem like the whole story
because something else is cropping the content just outside that div - the
content of the table seems to be overflowing the div with set height for a few
pixels at least

Comment 2

[Boris Zbarsky [:bzbarsky]]

The <div> with a set height is in a <td> and the <td> is what's cropping the text.

I'm not sure what we've decided to do with overflowing <td>s, really; hoping
bernd knows.

Comment 3

[Jason Barnabe (np)]

Attachment: Testcase

Comment 4

[HARUNAGA Hirotoshi]

Bug 208927 is a dup of this?

Comment 5

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

It doesn't matter, since they should both be fixed by bug 173277.

Comment 6

[Mats Palmgren (inactive)]

FIXED by bug 173277