Closed Bug 30332 Opened 25 years ago Closed 25 years ago

ROWSPAN = "0" tretaed differently than NS 4.x

Categories

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

x86
Windows 95
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: bluemonkey, Assigned: karnaze)

References

()

Details

(Keywords: testcase)

Attachments

(1 file)

Mozilla does not seem to correctly handle a keyword of ROWSPAN="0" in a <td> tag. On the page http://members.xoom.com/scrows the top middle cell, containing the "updates" graphic and the cell to it's left containing the stylized exclaimation point contain the ROWSPAN="0" keyword in their <td> tags. I saved this page locally and deleted all the embedded tables leaving only the outside table(this did not fix the problem). Then I chaned both of the above mentioned keywords to ROWSPAN="1" and the table displayed properly.
Can you attach that testcase to this bug report (Use the "create an attachment" link)?
Attached file Testcase showing ROWSPAN="0" problem (deleted) —
Bug confirmed in Build ID: 2000030913. D/L on 03/10/2000
Thanks, bluemonkey. <tr> <td ROWSPAN = "0">One</td> </tr> <tr> <td>Two</td> </tr> Mozilla lays out these two cells side-by-side, while NS 4.7 lays them out on top of each other. From the HTML spec: rowspan = number [CN] This attribute specifies the number of rows spanned by the current cell. The default value of this attribute is one ("1"). The value zero ("0") means that the cell spans all rows from the current row to the last row of the table section (THEAD, TBODY, or TFOOT) in which the cell is defined. If I read this right, then Mozilla is doing the right thing (making the first cell span the entire first column), and NS 4.7 is doing it wrong. Compatibility issues with NS 4.7?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: 4xp, testcase
Summary: ROWSPAN = "0" causes incorrect layout → ROWSPAN = "0" tretaed differently than NS 4.x
rowspan/colspan=0 now only works according to HTML 4 in strict mode. There are pages relying on the behavior where a value <= 0 becomes 1.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Verified on Linux build 2000.03.17.08. NS 4.7 behavior in for transitional doctype, conforming to spec in strict doctype.
Verified fixed.
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: