When using the <noframes> Tag in a <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> page the browser shows the text within the <noframes> area.
German example can be viewed at http://selfhtml.teamone.de/html/frames/anzeige/frames2.htm
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> isn't the correct doctype for a Frameset http://selfhtml.teamone.de/html/frames/anzeige/frames2.htm WFM with 20020731 on linux (Btw: it has another doctype!) .. Could you provide a testcase for this?
The frameset is defined as "-//W3C//DTD HTML 4.01 Frameset//EN" and the browser does not show the text within <noframes> which is correct. But if a browser does not support frames the <noframes> Tag can be used for those browsers on _every page_ to enable navigation for them (e.g.). Therefore the <noframes> Tag should not be ignored in other doctypes, such as "-//W3C//DTD HTML 4.01 Transitional//EN".
In reference to comment 2, the 4.01 spec specifically says that NOFRAMES can be used in a non-frameset DTD: "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." <http://www.w3.org/TR/html4/present/frames.html#edef-NOFRAMES" I attached a minimal testcase. However, this whole bug dups bug 47658 in any event. *** This bug has been marked as a duplicate of 47658 ***
My mistake. This is a related issue, but not a dup. Reporter, if you are really seeing the NOFRAMES text, that is actually correct according to the spec. I'm surprised if you are, because it doesn't happen for anyone else. What build are you using?
Bill: I do see "This is testing text in the body tag. This is test text in the noframes tag." I am using 1.0 build 2002053012. This is perfectly correct. However when this page is viewed as part of a frameset I should not see the second part. That is the problem.
Ok, then going back to your URL that you supplied, when I view that frameset it WFM in 2002072204 PC/Win98. I do not see the NOFRAMES content. Gunni, if you update to a current build, does this problem persist? Updating bug summary to clarify the issue at hand. Removed testcase kw since this testcase really doesn't address the issue.
Text enclosed by noframe should *never* appear in Mozilla, since Mozilla supports frames... I think you got that wrong in comment 6, Bill. otherwise: wfm on 2002072508 on winxp
Referencing comment 9: as I said, if you read the 4.01 spec there is a specific case cited in the spec where the <noframe> content should be visible. See my quote in comment 5. The fact that Mozilla does not do it is what bug 47658 is all about. This bug however is not about that issue. I thought initially it was since the bug description was not clear and the comments that followed confused me as well.
I imagine that the patch to bug 134401 fixed this. One could argue make a case for ignoring the example in the HTML standard as the rest of the text doesn't seem to support it, or interpret the rest of the text in the light of it as Bill (and others) have done. I doubt we will agree which is correct...
Sorry to Bill and thanks to Richard for making it clear. "User agents that support frames must only display the contents of a NOFRAMES declaration when configured not to display frames." versus "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." I sent an email about this issue to email@example.com which is the proper place to send in errata of HTML Specifications according to the spec itself.
That is the reply... It's their "bugzilla". I'll keep you posted, if I get any updates. Your issue has been added to the W3C's HTML Working Group Issue Tracking System. If you have further information about this issue to report, please reply to this message so that the additional data can be automatically attached to the original query. If you would like to check on the status of this issue, select the following link: http://hades.mn.aptest.com/cgi-bin/voyager-issues?selectid=719 This link will take you to a page that shows all the categories of problems tracked in the system. The category in which your problem report is held (initially called Incoming) will have the number "1" next to it, and all others will have the number "0". Select the link to the category to see your problem report, its status, any follow-up messqages, etc. If you would like to check on the other issues in the system, you can do so via the web at http://hades.mn.aptest.com/voyager-issues
Does this bug need to be kept open, if so is there a better component for it to be in and can it be confirmed? Otherwise it probably just needs marking as WFM
well, it is WFM on build 2002081018, winxp does anybody still see the bug on a recent build?
the page in the url has been updated to use a frameset doctype, so before you wfm this bug you should get a test case which tests the reported bug. attachment 93574 [details] doesn't quite test a frameset page with noframes and a transitional doctype.
Created attachment 96066 [details] testcase 2 modified version of http://selfhtml.teamone.de/html/frames/anzeige/frames2.htm with transitional doctype with no uri.
Yep, WFM WinXP 2002120608. This was a dup anyway.