Closed Bug 180334 Opened 22 years ago Closed 20 years ago

###!!! ASSERTION: attribute encountered -- this shouldn't happen unless the attribute was not part of a start tag!

Categories

(Core :: DOM: HTML Parser, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 142965

People

(Reporter: timeless, Assigned: harishd)

References

()

Details

(Keywords: assertion)

cvs build (source from a few days ago), building testparser requires a patch to
the tests Makefile, but the same assert happens on linux and in mozilla

I:\build\mozilla\dist\bin>testparser test_1115.html null
Type Manifest File: I:\build\mozilla\dist\bin\components\xpti.dat
###!!! ASSERTION: attribute encountered -- this shouldn't happen unless the
attribute was not part of a start tag!: 'Error', file
i:/build/mozilla/htmlparser/src/CNavDTD.cpp, line 2256
^ happens five times

###!!! ASSERTION: unsupported leaf node type: 'Not Reached', file
i:/build/mozilla/htmlparser/src/nsLoggingSink.cpp, line 717
^ if necessary, we can address this additional assert in another bug.

note that viewsource on this url apparently causes even more assertions (bug 180329)
Depends on: 180336
>#!!! ASSERTION: attribute encountered -- this shouldn't happen unless the
>attribute was not part of a start tag!: 'Error', file

This particular assertion is harmless. It just means that attributes were found
in tags other than start tag. Please ignore this assertion.

>###!!! ASSERTION: unsupported leaf node type: 'Not Reached', file
>i:/build/mozilla/htmlparser/src/nsLoggingSink.cpp, line 717

This was due to bug 167493. Should be fixed now.
Keywords: assertion
>This particular assertion is harmless
er, so why is it an assertion?
Er, unless that's a file specifically to test for our support of this quirk,
doesn't the file need fixing?
chb@frodo:/tmp$ egrep '</[^>]+=' mlp_status.html 
chb@frodo:/tmp$

--> I can't find the place of the file that would trigger this assertion - no
end tag in the file seems to have attributes.

Can I somehow find out which part of the file triggers that assertion? (without
manually truncating the file until it no longer shows up)
>This particular assertion is harmless
>er, so why is it an assertion?

I do hit the assertion for the follwing testcase:

<html><body>
<table>
<p><h3>Please Enter your Homesite Login, E-mail and Password to delete</h3></p>
<form method="POST">
<input type=submit>
</form>
</table>
</body></html>

so...have to take my word back. That's the assertion is real and needs attention. 

Note: I'll figure out what's going on with the above testcase.
FWIW, I just ran across this assertion at
<http://freetype.sourceforge.net/freetype2/docs/glyphs/glyphs-4.html>.
For another testcase, try almost anything at www.mapquest.com, where I'm getting 
this with a debug build (built yesterday). To echo a previous comment, could 
this assertion be modified to inform the user of what attribute it doesn't like? 
That way it would be easy to tell if I need to do some evangelism at Mapquest, 
or just watch this bug.
*** Bug 240121 has been marked as a duplicate of this bug. ***
Reported at http://www.netscape.com/ in the dupe bug.
The testcase in comment 5 comes right from bug 142965, marking as a duplicate.

*** This bug has been marked as a duplicate of 142965 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.