118718 - noframes treated like "view source" when used out of frameset

Status: RESOLVED DUPLICATE of bug 134401

(Core :: Layout: Images, Video, and HTML Frames, defect)

Description

[unapersson]

If a noframes tag is used on a page that is not in a frameset, then it 
displays the HTML source of the content of the noframes tag. See testcase for an
example.

Comment 1

[Christopher Aillon (sabbatical, not receiving bugmail)]

Uhm, what testcase?

Comment 2

[unapersson]

Attachment: Demonstration of current behaviour

Comment 3

[Daniel Brooks [:db48x]]

Isn't the noframes tag illegal outside a frameset anyway?

Comment 4

[unapersson]

Quite possibly, but in that case the tag should be ignored and the content shown
as usual, not as html.

Comment 5

[unapersson]

I've just checked the HTML4.01 specification, and according to that the content
in the testcase should be displayed:

http://www.w3.org/TR/html4/present/frames.html#h-16.4.1

"NOFRAMES may be used, for example, in a document that is the source of a frame
and that uses the transitional DTD. This allows authors to explain the
document's purpose in cases when it is viewed out of the frameset or with a user
agent that doesn't support frames."

Comment 6

[Matthias Versen [:Matti]]

*** Bug 121196 has been marked as a duplicate of this bug. ***

Comment 7

[Julien Cegarra]

unapersson: contents yes but not the source.

/jc

Comment 8

[Manfred Becker]

But it shows the source also when the page is the source of a frame, and that is
also a bug !

Comment 9

[Kevin McCluskey (gone)]

Bulk re-assigning all of Eric's HTMLFrame bugs to John.

Comment 10

[ansgar wiechers]

i have reproduced this behaviour with mozilla 0.9.7 and 0.9.8 on windows 98 and
mozilla 0.9.8 on windows 2000. mozilla 0.9.6 does not seem to be affected.

the bug seems to only affect the first appearance of <noframes>...</noframes>
and leads to displaying the source between these tags, regardless of the page
being displayed as part of a frameset or as a single page.

i put up a demonstration on my homepage [1].

regards
ansgar wiechers (59cobalt)

[1] http://www.planetcobalt.net/other/mozilla-noframes.html

Comment 11

[Jacob Kjome]

Hmm... using <noframes> outside a frameset is legal html, but how commonly is 
this used and when would this be useful?  Everything work just fine if 
<noframes> is used in the context it normally takes place within; a frameset.  
w3c validated testcase coming up that works just fine in Mozilla.

Jake

Comment 12

[Jacob Kjome]

Attachment: more common use of noframes

Comment 13

[unapersson]

You can use it for navigation and/or html fragments that will only appear when a
page is viewed:

1) outside a frameset, i.e. when you hit the page from a search engine
2) with a browser that doesn't support frames

Comment 14

[Marc Attinasi]

This looks to me to be a parser or content sink problem. Here is the content
model for the first testcase:

html@030B76B0 refcount=10<
  head@030B77A8 refcount=2<
    title@030D1808 refcount=2<
      Text@030D1860 refcount=2<Noframes tag>
    >
  >
  Text@030CCE20 refcount=3< \n\n\n>
  body@030D1AA8 refcount=4<
    Text@030F1278 refcount=3<\n>
    p@030F1328 refcount=3<
      Text@030F1380 refcount=3<Paragraph>
    >
    Text@030F1440 refcount=3<\n>
    noframes@030F1538 refcount=3<
      Text@030CCF28 refcount=4<\n<p>Paragraph in No Frames
Tag</p>\n<ul>\n<li>Bulleted List \n<li><a href="http://www.mo
zilla.org/">Mozilla</a>\n</ul>\n>
    >
    Text@030F1590 refcount=3<\n>
    p@030F15E8 refcount=3<
      Text@030F1640 refcount=3<Paragraph>
    >
    Text@030BB800 refcount=3<\n>
  >
>

As you can see, the contents of the NOFRAMES container is sent in as a text
node, so no wonder layout treats ot as such.

Comment 15

[Marc Attinasi]

Hmm. It also looks like the content sink creates a DIV content element in the
continer for the NOFRAMES tag, which has me really confused.

Comment 16

[Dan Tobias]

This may be related to Bug 122077 (even though that one has been fixed)... I
think all of these problems stem from the way the NOFRAMES content is being
treated, apparently as raw text rather than HTML markup.

Comment 17

[Juergen Keil]

I don't know where this error comes from but I know that this 
prevents me from using Mozilla as my standard browser.
I tried it out using Win98, NT4 and XP not only on the first occurence
of the noframes tag but on the second or third as well.
It then works properly for no known reason (at least for me :-) ).
Have a look at http://home.arcor.de/lispm/audio/main.html .

Comment 18

[Boris Zbarsky [:bzbarsky]]

This is long since fixed.  The fix will be in 1.1 and 1.0.1

*** This bug has been marked as a duplicate of 134401 ***