Closed Bug 155722 Opened 23 years ago Closed 23 years ago

parser drops <! at beginning of comment

Categories

(Core :: DOM: HTML Parser, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 144902

People

(Reporter: bc, Assigned: harishd)

References

()

Details

Steps to reproduce: 1. view site in Mozilla rv:1.0.1 Gecko/20020702 or rv:1.1a+ Gecko/20020702 using win2k Expected Results: No comment source appears in page Actual Results: -- end header -----------------------------------------------------> appears in Mozilla, but not in IE6. Looking in the source the comment is missing the beginning <! in Mozilla but not in IE6 or in <http://webtools.mozilla.org/web-sniffer/view.cgi?url=http%3A%2F%2Fwww.seaburychicago.com%2Fdefault_r.asp> This is an IIS4 site. I changed UA String to IE5.5 and IE6 in Mozilla but still got the same result, so I don't think this is server side sniffing related. Note the page uses DOCTYPE: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Final//EN">
the code is equivalent to <!-- end header -> (which is evang worthy) have you tried saving the file to disk in IE and using that?
saved to disk using IE6 and viewed in Mozilla still drops the leading <! in view source. using the 'source generator sidebar' from mozilla-evangelism.bclary.com shows what is happening in the DOM. This is what the DOM thinks it saw: <TD align = "left" valign = "top"> <!----> -- end header -----------------------------------------------------> The comments in standards mode are definite evang fodder, but what is happening here?
cc'ing heikki. is this from those changes to comment parsing?
Apparently, the strict comment parsing code is not able to find the comment end and therefore we end up treating the "comment" as text. However, the code failed to include <! before bailing out.
btw, looks like switching to quirks mode still exhibits the bug.
*** This bug has been marked as a duplicate of 144902 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verifying
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.