Closed Bug 43820 Opened 26 years ago Closed 22 years ago

malformed script tags in frameset head causes parser to screw up

Categories

(Core :: DOM: HTML Parser, defect, P3)

x86
Windows NT
defect

Tracking

()

RESOLVED WORKSFORME
Future

People

(Reporter: ianm, Assigned: harishd)

References

()

Details

(Keywords: compat, Whiteboard: INVALID?)

Attachments

(1 file)

From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt) BuildID: 2000062408 using javascript in the head portion of a frameset causes parsing irregularities for the frameset itself. Here is the sample frameset html: <html> <head> <title></title> <script language="javascript"> var arrFrames = new Array(); function frameRegister(fram) { var txt = "top.arrFrames['" + fram.name + "'] = fram;"; eval(txt); } </script </head> <frameset cols="150,623,*" framespacing="0" border="0" frameborder="0"> <frame name="menu" src="test/testMenu.html" marginwidth="0" marginheight="0" scrolling="no" noresize="true"></frame> <frameset rows="75,30,30,*,60" framespacing="0" frameborder="0" border="0" > <frame name="title" src="test/testTitle.html" marginwidth="0" marginheight="0" scrolling="no" noresize="true"></frame> <frame name="top" src="test/testTop.html" marginwidth="0" marginheight="0" scrolling="no" noresize="true"></frame> <frame name="header" src="test/testHeader.html" marginwidth="0" marginheight="0" scrolling%
i think i have a url for this problem... http://silva.at/content/e_main.html could you check if this is the same problem Ian ? Adding myself to CC list.
i´ve tested the html above and all i get was following: var arrFrames = new Array(); function frameRegister(fram) { var txt = "top.arrFrames['" + fram.name + "'] = fram;"; eval(txt); } no frames were visible. there is an error in the html -> the closing tag for script is not correct. </script missing > - when closing script tag is correct written ( </script> ), frames are visible. marking invalid due error in html code.
Status: UNCONFIRMED → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
Reopen to bring back on radar, might be of interest.
Status: RESOLVED → UNCONFIRMED
Component: HTMLFrames → Parser
Resolution: INVALID → ---
Handing this to you Harish. Don't know if this is a big deal or not, but you might be interested in how Nav and IE handle this malformed case vs. how we do. It is malformed though, so probably Future? Horwath Martin: Thanks for narrowing down the problem!
Assignee: pollmann → harishd
A very low priority issue. Moving to FUTURE list.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Future
Target Milestone: Future → mozilla0.9.1
This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug,or if it blocks your work in some way -- please attach your concern to the bug for reconsideration -----
Target Milestone: mozilla0.9.1 → Future
"</script" is missing its TAGC, I don't think we should worry about this.
Severity: normal → trivial
Keywords: compat
Summary: script tags in frameset head causes parser to screw up → malformed script tags in frameset head causes parser to screw up
Whiteboard: INVALID?
Attached file Testcase
This worksforme in a current build.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago22 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: