Closed Bug 889 Opened 26 years ago Closed 25 years ago

parser not handling illegal content within table

Categories

(Core :: DOM: HTML Parser, defect, P2)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: buster, Assigned: harishd)

References

()

Details

"front" and "back" content is lost. Third cell is placed after the table as a second table with a single cell. ---------------- test case ---------------- <TABLE border="2"> front <TR> <TD> <TABLE border="2"> <TR><TD>1</TD></TR> <P></P> </TABLE> <TABLE border="2"> <TR><TD>2</TD></TR> </TABLE> </TD> <TD> Lorem<BR>ipsum<BR>dolor </TD> </TR> back </TABLE>
Status: NEW → ASSIGNED
Setting all current Open/Normal to M4.
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Assignee: rickg → harishd
Status: ASSIGNED → NEW
I've a fix for handling bad-contents in table. Will check it in soon after I clear some memory leaks. Reassigning the bug to myself and adding rickg to the CC list.
Target Milestone: M4 → M5
Have a fix for handling illegal contents in table. However, I got to do a lot more testing that would not be possible within the M4 time frame. So, moving the milestone to M5.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Checked in fix to handle illegal-contents within tables. Marking the bug fixed.
QA Contact: 3847 → 4141
Attempting to steal gem's HTMLParser bugs all at once. Changing QAContact to janc.
Status: RESOLVED → VERIFIED
Verified Fixt in build 1999-05-25-17-M6 on WinNT and Win98
Depends on: 75338
No longer depends on: 75338
Depends on: 75338
No longer depends on: 75338
You need to log in before you can comment on or make changes to this bug.