Closed Bug 2947 Opened 26 years ago Closed 26 years ago

Table width wrong caused by colspan/img/overflow

Categories

(Core :: Layout, defect, P2)

x86
Windows 95
defect

Tracking

()

VERIFIED DUPLICATE of bug 3977

People

(Reporter: dbaron, Assigned: karnaze)

References

()

Details

The inner nested table in the above URL is sized incorrectly, I think. This makes the form and the image overflow widthwise.
Assignee: troy → karnaze
Status: NEW → ASSIGNED
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Target Milestone: M7
Moving to M7.
Moving to M9.
This is basically a dup of bug 1110.
*** Bug 1110 has been marked as a duplicate of this bug. ***
Summary: display problem related to sizing nested tables → Table width wrong caused by colspan/img/overflow
[TESTCASE] Here is a broken down test case: http://www.bath.ac.uk/%7Epy8ieh/internet/projects/mozilla/tablesizing.html This is a *very* weird bug. The test case is self explanatory, but basically, the 'width' of a table is approximately halved in certain situations involving colspans, images, and cell contents overflowing. I removed the nested table without affecting the bug, so I am removing 'nested tables' from the summary.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 3977 ***
Ian - please don't change the URL without noting it in the text. Otherwise the comments above the URL change don't make sense, and the URL is lost for verification. The original URL was http://www.webstandards.org/ , which Ian changed to his test case above.
David: Sorry about that, I had no intention of oblitarating the URL. I've put it back to the original bug report address. Must have been holding the wrong text in the clipboard, and pasted it in the wrong box, or something... (I'm so used to Emacs' kill ring that single-clipboard systems confuse me...)
Status: RESOLVED → VERIFIED
Verified Dup
You need to log in before you can comment on or make changes to this bug.