Closed Bug 66468 Opened 25 years ago Closed 24 years ago

extra space in table with invalid tag

Categories

(Core :: DOM: HTML Parser, defect)

Product:
Core
Component:
DOM: HTML Parser
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED WONTFIX

People

(Reporter: basic, Assigned: attinasi)

References

Details

(Keywords: testcase)

Attachments

(1 file)

testcase refered by the above comment
210 bytes, text/html
Details
Build ID: 2001011904 In this nightly build the to be attached testcase is displayed with an extra space. The extra space is not found in M 0.7 build
Confirmed on Win 98 build 2001012404. Observed: Bad HTML between the opening "table" and "tr" tags causes space to appear between the table border and the table row. Expected: Mozilla should ignore the bad HTML and display the table properly.
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA contact update
QA Contact: chrisd → amar
still seeing this on mozilla0.9 win32 talkback
It appears that from Bug 88490 this also affects invalid tags following a <tr>.
*** Bug 88490 has been marked as a duplicate of this bug. ***
We're probably putting the tag in the content model and then handling it as unknown content within a table. Maybe the parser should be doing something different for unknown tags within tables?
Looks like parser. Sending over.
Assignee: karnaze → harishd
Component: HTMLTables → Parser
Keywords: testcase
OS: Windows 98 → All
QA Contact: amar → bsharma
looks like its fixed in the latest nightly. The "unknown" element is now placed above the table (in the DOM at least). I don't see any space above the cell anymore
forgot to mention that this was tested with build 2001092103 win32 note that it causes the table to be shifted about 1em lower than it normally would be at.
err... scratch that comment about the table being 1em lower...
QA Contact: bsharma → moied
Unknown tags have no clear definition of how they should get treated. A while ago there was a bug, forgot the bug#, which indicated that unknown tags should not be thrown out of tables and now this bug contradicts that. I don't have a clear answer of what should be done in this case. May be layout can avoid creating frames for unknown tags ( not sure what layout does with unknown tags ) or may be we can evangelize the site. Giving bug to Marc for more input.
Assignee: harishd → attinasi
I really do not see a problem here - what is the bug? The testcase renders just like IE, so for compat. we are OK. We create an inline frame for unknown content - that is the default display type. IN this testcase that frame is empty, but in others I have seen you can style it and get all kinds of cool non-standard things to happen. So, I do not see extra space in the cell, the inline for the bad tag has no width or height. Also, I see no URL to check or evangelize...
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
When I first filed this bug there was a seperate bug filed for evang (can't remember the bug # as it was 8 months ago). Back then the <bad html> appeared as an inline frame that had a height of about 1em within the table. Now the <bad html> is an empty frame (that has no height) *before* the table.
OK, so there is really nothing here to fix. Thanks.
Tested with Build ID 20011130, IE and Opera 5.12 renders the same Marking verified WONTFIX
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: