Closed Bug 225534 Opened 21 years ago Closed 21 years ago

string "</SCRIPT>"(closing SCRIPT tag) within script section breaks script loading

Categories

(Firefox :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 32618

People

(Reporter: nobu.hirashima, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7

maybe related to bug #66013, but not exactly a duplicate...

When there is string "</SCRIPT>" written in javascript section,
the script loading ends there, thus breaking code execution.
I think we've seen this bug in NN4.  Is this by design?

There's an intranet app that does dynamic html building & displaying
with javascript.  Some of its pages work with IE6SP1 but doesn't
work with Firebird0.7, showing off javascript codes in such pages.

See the reproducing codes for details.

Reproducible: Always

Steps to Reproduce:
1.bad code.

<script language=javascript>

var html = '<html><head><title>abc</title></head>'
	+ '<body>'
	+ 'abcde'
	+ '<script language=javascript>'
	+ '</script>'    //NG
	+ '</body></html>'
	document.write(html);

</script>

2. good code
*note the whitespace within the closing script tag

<script language=javascript>

var html = '<html><head><title>abc</title></head>'
	+ '<body>'
	+ 'abcde'
	+ '<script language=javascript>'
	+ '</ script>'   //space inside
	+ '</body></html>'
	document.write(html);

</script>

Actual Results:  
1. no HTML title, page displays javascript code bits.
> ' + '' document.write(html);

2. HTML title is "abc", page displays normally.
> abcde

Expected Results:  
case 1 should display "abcde" as well.
Add HTML comments to work around.

<script>
<!---
whatev
-->
</script>

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