By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,696 Members | 1,462 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,696 IT Pros & Developers. It's quick & easy.

HTMLParser chokes on bad end tag in comment

P: n/a
The code below results in an exception (Python 2.4.2):

HTMLParser.HTMLParseError: bad end tag: "</foo' + 'bar>", at line 4,
column 6

Should it? The end tag it chokes on is in comment, isn't it?

import HTMLParser
HTMLParser.HTMLParser().feed("""
<html><head><title></title></head><body><script>
<!--
x = '</foo' + 'bar>'
// -->
</script></body></html>
""")

--
René Pijlman
May 28 '06 #1
Share this Question
Share on Google+
6 Replies


P: n/a
Rene Pijlman wrote:
The code below results in an exception (Python 2.4.2):

HTMLParser.HTMLParseError: bad end tag: "</foo' + 'bar>", at line 4,
column 6

Should it? The end tag it chokes on is in comment, isn't it?


no. STYLE and SCRIPT elements contain character data, not parsed
character data, so comments are treated as characters, and the first
"</" ends the element.

if you have broken documents, you can tweak this by setting the
CDATA_CONTENT_ELEMENTS parser attribute before you start parsing.

</F>

May 29 '06 #2

P: n/a
Fredrik Lundh:
Rene Pijlman:
[end tag in html comment in script element]
The end tag it chokes on is in comment, isn't it?

no. STYLE and SCRIPT elements contain character data, not parsed
character data, so comments are treated as characters, and the first
"</" ends the element.
Ah, I see. I'll report the problem to the application that's generating
this broken code (vBulletin forum)...
if you have broken documents, you can tweak this by setting the
CDATA_CONTENT_ELEMENTS parser attribute before you start parsing.


.... and in the mean time that's a good workaround.

Thank you very much Fredrik.

--
René Pijlman
May 29 '06 #3

P: n/a
Hello Rene,

You can also check out BeautifulSoup
(http://www.crummy.com/software/BeautifulSoup/) which is less strict
than the regular HTML parser.

HTH,
Miki
http://pythonwise.blogspot.com/

May 29 '06 #4

P: n/a
Miki:
You can also check out BeautifulSoup
(http://www.crummy.com/software/BeautifulSoup/) which is less strict
than the regular HTML parser.


Yes, thanks. Ik this case it was my sitechecker which checks for syntax
and broken links, so it was supposed to find the syntax error.
BeautifulSoup is not very well suited for validators :-)

--
René Pijlman
May 29 '06 #5

P: n/a
Fredrik Lundh wrote:
Should it? The end tag it chokes on is in comment, isn't it?


no. STYLE and SCRIPT elements contain character data, not parsed
character data, so comments are treated as characters, and the first
"</" ends the element.


Rather than take your word for it, I checked the W3C HTML4 DTD and found
this:

http://www.w3.org/TR/html4/appendix/...pecifying-data

Element content

When script or style data is the content of an element (SCRIPT and STYLE),
the data begins immediately after the element start tag and ends at the
first ETAGO ("</") delimiter followed by a name start character ([a-zA-Z]);
note that this may not be the element's end tag. Authors should therefore
escape "</" within the content. Escape mechanisms are specific to each
scripting or style sheet language.

ILLEGAL EXAMPLE:
The following script data incorrectly contains a "</" sequence (as part of
"</EM>") before the SCRIPT end tag:

<SCRIPT type="text/javascript">
document.write ("<EM>This won't work</EM>")
</SCRIPT>

In JavaScript, this code can be expressed legally by hiding the ETAGO
delimiter before an SGML name start character:

<SCRIPT type="text/javascript">
document.write ("<EM>This will work<\/EM>")
</SCRIPT>
Guess you learn something new every day. Too bad there's so much illegal
code in the wild. :(

--
Edward Elliott
UC Berkeley School of Law (Boalt Hall)
complangpython at eddeye dot net
May 29 '06 #6

P: n/a
Edward Elliott wrote:
Guess you learn something new every day. Too bad there's so much illegal
code in the wild. :(


if more people learned something new every day, the wild would look a
lot different.

</F>
May 29 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.