Closed Bug 2779 Opened 26 years ago Closed 24 years ago

{compat} cellpadding and cellspacing not working

Categories

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

x86
Windows 95
defect

Tracking

()

VERIFIED DUPLICATE of bug 15499

People

(Reporter: bkdelong, Assigned: karnaze)

References

()

Details

(Whiteboard: (04/07) 3jrgm@qlink.queensu.ca -- review complete (test case filed))

Attachments

(1 file)

Table cellpadding and cellspacing works fine in NN4.5 but not NGLayout build from 1/26/99
<!-- Actually, it is not a problem with cellpadding/cellspacing. Drop this test case into a browser and you can see that the 2 images in the top-right TD are stacking vertically and *not* horizontally; hence, the visual gap in NGLayout. (Look for the small black square (border)). The TABLE is width 551; the IMG in the TD of the first row have width (67 + 338 + 142 = 547px) and the spacer.gif is 'width=4' in the original page, so this should fit as intended. (Counting available space is off by one (or two)??). ====================================================================== --> <html><head><base href="http://www.tompeters.com/home.asp"></head> <body bgcolor="#ffcc33"> <table cellpadding="0" cellspacing="0" border="1" width="551"> <tr><td> <table border="0" cellpadding="0" cellspacing="0"> <tr> <td><img src="images/topleft.gif" width=67 height=101 border="0"></td> <td><img src="images/topmid.gif" width=338 height=101 border="0"></td> <td><!-- SPACER IMAGE GOES OUT OF LINE HERE if width == 1 and border=0, everything OK (no gaps) if width > 1 then this TD cell wraps the two images --><img src="images/spacer.gif" width="4" border="1"><img src="images/topright2.gif" border="0" width="142" height="101"></td> </tr> </table> <table border="0" cellpadding="0" cellspacing="0"> <tr> <td valign="top"><img src="images/botleft.gif" width=67 height=149 border="0"></td> <td valign="top"><img src="images/tpladder.gif" width="148" height="149" border="0"></td> </tr> </table> </td></tr> </table> </body> </html> <!-- ====================================================================== tested on nightly build Jan 29 win95 optimized (but is also the same for Jan 15 build). -->
Setting all current Open/Normal to M4.
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
Whiteboard: (04/07) 3jrgm@qlink.queensu.ca -- review complete (test case filed)
moving to m5
Target Milestone: M5 → M6
Moving to M6.
Moving to M8
Moving to M9.
Assignee: karnaze → kipp
Status: ASSIGNED → NEW
The url is no longer valid. Nav 4.x and IE5 treat the max element width of a nested table cell containing adjacent images with no whitespace between them as the combined max element widths of the images. This isn't the case if the table cell is in a non nested table. I've include an example below. Kipp, the table cell could tell its area frame that it is nested and then eventualy line layout could deal with this special case. I know this sucks, but can you think of a better way. the adjacent images in the nested table have no whitespace <table cellpadding="0" cellspacing="0" border="1" width="100"> <tr> <td> <table border="0" cellpadding="0" cellspacing="0"> <tr> <td> <img src="raptor.jpg" width=100 height=100 border="0"></td> <td> <img src=raptor.jpg width="25" border="1"><img src=raptor.jpg border="0" width="92" height="101"></td></tr> </table> </td> </tr> </table> <BR> the adjacent images in the nested table have whitespace <table cellpadding="0" cellspacing="0" border="1" width="100"> <tr> <td> <table border="0" cellpadding="0" cellspacing="0"> <tr> <td> <img src="raptor.jpg" width=100 height=100 border="0"></td> <td> <img src=raptor.jpg width="25" border="1"> <img src=raptor.jpg border="0" width="92" height="101"></td></tr> </table> </td> </tr> </table> <BR> the adjacent images in the non nested table have no whitespace <table width=100 border="0" cellpadding="0" cellspacing="0"> <tr> <td> <img src="raptor.jpg" width=100 height=100 border="0"></td> <td> <img src=raptor.jpg width="25" border="1"><img src=raptor.jpg border="0" width="92" height="101"></td></tr> </table>
Target Milestone: M9 → M10
Moving to M10.
Status: NEW → ASSIGNED
Target Milestone: M10 → M12
Summary: cellpadding and cellspacing not working → {compat} cellpadding and cellspacing not working
Target Milestone: M12 → M19
Assignee: kipp → karnaze
Status: ASSIGNED → NEW
I made a new test case with two outer tables. The first has two cells in the table width, such that the sum of the cell widths is greater than the table specified width (20+117 == 137). The second case is similar, except that the sum of the two cell widths ends up much larger than the specified table width (100+117 == 217). Navigator, for some reason, lays out the two tables very differently. I think that this is just another whacky compatability bug that we *don't* want to emulate. Giving to chris to make the final call about.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → LATER
I would implement the Nav4.6 quirk that Kipp mentions, but I can't figure out what it is. I tried several different values of width in his example and still couldn't find a hint. IE5 doesn't do any better than Gecko, it does the 2nd table like Nav4.6 but does the 1st one wrong. IE5 must have tried to imitate this very quirky behavior and didn't quite get it right. I'm marking this "later".
Status: RESOLVED → VERIFIED
Verified LATER.
it's a dup
Status: VERIFIED → REOPENED
Resolution: LATER → ---
*** This bug has been marked as a duplicate of 15499 ***
Status: REOPENED → RESOLVED
Closed: 25 years ago24 years ago
Resolution: --- → DUPLICATE
Verified dup of #15499
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: