Closed Bug 4739 Opened 26 years ago Closed 25 years ago

Collapsing cells does not calculate %ge widths correctly

Categories

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

x86
Windows 95
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: run2000, Assigned: karnaze)

References

()

Details

(Whiteboard: [TESTCASE] -- run2000@geocities.com)

Attachments

(1 file)

The behaviour occurs on the 7 April 1999 optimized build, on Win 95 OSR 2. Also see it on Win 98, and Win NT4 Workstation with SP4. The URL above consists of a table which should always cover 100% of the screen width. What should happen: * Brown background of table should always cover the entire width of the browser window. * Right hand images should always be at the right-hand edge of the table What actually happens: * When the browser window is sized somewhere between 540 pixels (the sum of all adjacent images) and 680 pixels (the width in pixels stated in the table cells) the table gets 'stuck' at 540 pixels. * When the browser window is resized to over 680 pixels, the table resizes normally.
Status: NEW → ASSIGNED
Target Milestone: M7
Moving to M7.
Moving to M9.
Whiteboard: [MAKINGTEST] - run2000@geocities.com
Summary: [4.xP] Table sizing weirdness → Collapsing cells does not calculate %ge widths correctly
Whiteboard: [MAKINGTEST] - run2000@geocities.com → [TESTCASE] -- run2000@geocities.com
The test case attached is a simple table containing two cells, one a fixed width cell, the other a percentage width cell. The problem is related to the collapsing cell model used in Mozilla. When the window size is wide enough to display the fixed width cell at its full width, the other cell resizes correctly. When the window size is no longer wide enough to accommodate the fixed width cell, the entire table collapses. This would indicate that the display size of the second cell is being calculated before the first cell has been collapsed. The fix is to calculate the width of the second cell after the first cell is collapsed.
Fixed with 7/28 changes.
Chris K: Is this fixed? If so, please mark as such. Thanks
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Using 10/20 app, verified bug fixed.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: