Framesets not recognised when improperly nested

VERIFIED FIXED

Status

()

Core
HTML: Parser
P3
normal
VERIFIED FIXED
18 years ago
18 years ago

People

(Reporter: dwindlehop, Assigned: harishd)

Tracking

Trunk
x86
Other
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [TESTCASE], URL)

Attachments

(3 attachments)

(Reporter)

Description

18 years ago
Trying this URL with the last build of Aug 17 gives the following error:

If you are not able to see this page, it is because your browser doesn't
support the frames feature, acquire a frames capable browser to view
this page.

Updated

18 years ago
Assignee: karnaze → pollmann

Comment 1

18 years ago
Reassigning to Eric.

Updated

18 years ago
Whiteboard: [MAKINGTEST] -- run2000@geocities.com

Comment 2

18 years ago
Created attachment 1293 [details]
Testcase showing frameset improperly contained in BODY element.

Comment 3

18 years ago
Created attachment 1294 [details]
Testcase showing frameset contained in unknown element.

Comment 4

18 years ago
Created attachment 1295 [details]
Testcase showing frameset contained in element that is child of the HEAD element.

Updated

18 years ago
Summary: Site does not recognize Mozilla as a frames-capable browser → Framesets not recognised when improperly nested
Whiteboard: [MAKINGTEST] -- run2000@geocities.com → [TESTCASE]

Comment 5

18 years ago
Tested on Apprunner, build 1999081709 (M9), on Windows 95.

The problem appears to be that the frameset is improperly nested inside some
other element. It doesn't appear to matter that the element is not a known HTML
element. The notable case that may cause many existing pages to break is when
the frameset is a child of the BODY element.

Strangely, if the frameset is a child of the HEAD element, or some other element
that is a child of the HEAD element, the frameset works as expected.

Comment 6

18 years ago
This problem may also be related to bug 9059.

Updated

18 years ago
Assignee: pollmann → harishd

Updated

18 years ago
Component: HTMLFrames → Parser

Comment 7

18 years ago
Harish, these are some more malformed cases where framesets are not put in the
content model.

The first case doesn't work in Nav, IE, or Gecko.

The second case works in Nav and IE but not Gecko - this is the one that we
should maybe look at correcting.

The third case works in all three.

Can you take a look?  Thanks!
(Assignee)

Updated

18 years ago
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
(Assignee)

Comment 8

18 years ago
Fix is in:)  We should be ok...

Marking bug fixed.

Updated

18 years ago
Status: RESOLVED → VERIFIED

Comment 9

18 years ago
the first attached test case does not render as described. However, since it is
malformed HTML, it should not render as the reporter believes it should. The DTD
explicitly states that a frame/frameset is not allowed within the BODY element.
An HTML file is either comprised of the BODY element or the FRAMESET element.
The other two render correctly.
You need to log in before you can comment on or make changes to this bug.