49551 - when extraneous </script> is encountered, explain bug 32618

Status: NEW

(Core :: DOM: HTML Parser, enhancement, P5)

Description

[Jesse Ruderman]

so that people don't keep reporting mozilla's correct behavior of interpreting 
document.write("</script">) as the end of a script let's report an error to the 
user.  (see bug 18324, bug 21944, bug 26857, bug 32618, and bug 49449)

mozilla encountered an extraneous </script>.  this often happens when webpage 
authors forget to escape the string "</script>" as "<\/script>" within a 
script, since some older browsers (including older versions of netscape (?)) 
incorrectly pretended that it was escaped anyway.  for more information see 
http://bugzilla.mozilla.org/show_bug.cgi?id=32618.

this is a special case of bug 6211.

Comment 1

[Kevin McCluskey (gone)]

Dividing up claytons bugs to triage.

Comment 2

[gerardok]

massive update for QA contact.

Comment 3

[Kevin McCluskey (gone)]

Harish, is this an error that the parser can emit?

Comment 4

[harishd]

This falls under  nice to have category..not a "must have". Marking FUTURE.

Comment 5

[Hixie (not reading bugmail)]

Reassigning QA Contact for all open and unverified bugs previously under Lorca's
care to Gerardo as per phone conversation this morning.

Comment 6

[bsharma]

qa contact updated.

Comment 7

[Heikki Toivonen (remove -bugzilla when emailing directly)]

SPAM. HTML Element component deprecated, changing component to Layout. See bug
88132 for details.

Comment 8

[Boris Zbarsky [:bzbarsky]]

The whole point is that we don't know it's an extraneous </script>.  If we did,
we'd just skip over it.

I feel this should be wontfix -- error reporting in the HTML parser just isn't
going to happen, imo.

Comment 9

[Jesse Ruderman]

If a page has

<script>
document.write("</script>");
</script>

then when the parser reaches the *second* </script>, there won't be a <script>
open, so it's clearly an extraneous </script>.

Comment 10

[Boris Zbarsky [:bzbarsky]]

Oh, so the real message you want output is "stray </script> tag encountered at
line X" (when the real error was at line Y)?

Even doing that in the current parser "architecture" is probably more trouble
than it's worth (especially given that error messages with unhelpful line
numbers aren't worth much).

Comment 11

[Jens Stutte [:jstutte]]

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority and severity.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.