Closed
Bug 24112
Opened 25 years ago
Closed 25 years ago
TFOOT rendered above TBODY
Categories
(Core :: Layout: Tables, defect, P2)
Tracking
()
VERIFIED
FIXED
M14
People
(Reporter: bugzilla, Assigned: harishd)
References
()
Details
(Keywords: html4)
If a table is specified with THEAD/TFOOT/TBODY row groups (in the correct order), Mozilla erroneously renders the TFOOT row group before the TBODY row groups rather than after. (It appears that Mozilla ignores row group tags altogether.) This is contrary to the HTML 4.0 specification: http://www.w3.org/TR/REC-html40/struct/tables.html
Reporter | ||
Updated•25 years ago
|
Summary: TFOOT rendered above TBODY [4.xP] → [4.xP] TFOOT rendered above TBODY
Reporter | ||
Comment 1•25 years ago
|
||
In nightly build 2000011508, when the optional closing tag </TFOOT> is omitted, any following <TBODY> groups appear as a subtable beneath the <TFOOT> group. When the </TFOOT> closing tag is included, the <TFOOT> group is correctly positioned after the <TBODY> groups.
Updated•25 years ago
|
Assignee: karnaze → harishd
Comment 2•25 years ago
|
||
Harish, the content model is wrong for <table border> <thead><tr><td>head <tfoot><tr><td>foot <tbody><tr><td>body </table>
The real problem here is that elements are being closed out properly. If you manually add the right close tags, the page lays out right. It looks like an autoclosure bug in the navDTD.
FIXED by adding TD|TH to the autoclose tag list of TBODY,THEAD,and TFOOT.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 5•25 years ago
|
||
Using 2/1 build, verifying bug fixed. Using the 1/16 small testcase, tbody renders above tfoot as expected.
Status: RESOLVED → VERIFIED
Reporter | ||
Updated•24 years ago
|
Reporter | ||
Comment 6•24 years ago
|
||
In accordance with "4xp for 'competitor products' Considered Harmful" thread on n.p.m.qa.general, stripping the [4.xP] off this bug, though it's moot now.
Keywords: html4
Summary: [4.xP] TFOOT rendered above TBODY → TFOOT rendered above TBODY
You need to log in
before you can comment on or make changes to this bug.
Description
•