RESOLVED CONFIGURATION CHANGED 44825
False warning: <noframes> is not allowed inside <frameset> 
https://bugs.webkit.org/show_bug.cgi?id=44825
Summary False warning: <noframes> is not allowed inside <frameset>
Doug Kramer
Reported 2010-08-28 11:44:05 PDT
On this page: http://download.oracle.com/javase/6/docs/api/index.html Web Inspector in Safari 5.0 (5533.16) and Chrome 6.0.(495.0 dev) both show this error: <noframes> is not allowed inside <frameset>. content ignored. This is the relevant HTML on index.html: -------------------------------------- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd"> <FRAMESET cols="20%,80%" title="" onLoad="top.loadFrames()"> <FRAMESET rows="30%,70%" title="" onLoad="top.loadFrames()"> <FRAME src="overview-frame.html" name="packageListFrame" title="All Packages"> <FRAME src="allclasses-frame.html" name="packageFrame" title="All classes and interfaces (except non-static nested types)"> </FRAMESET> <FRAME src="overview-summary.html" name="classFrame" title="Package, class and interface descriptions" scrolling="yes"> <NOFRAMES> This client does not support frames </NOFRAMES> </FRAMESET> -------------------------------------- This HTML seems to conform to the spec, quoted as follows http://www.w3.org/TR/html4/present/frames.html The NOFRAMES element is part of both the transitional and frameset DTDs. In a document that uses the frameset DTD, NOFRAMES may be used at the end of the FRAMESET section of the document. <FRAMESET cols="50%, 50%"> <FRAME src="main.html"> <FRAME src="table_of_contents.html"> <NOFRAMES> </NOFRAMES> </FRAMESET> I suspect this is a WebKit bug. Others have run across the same problem: http://www.google.com/support/forum/p/Chrome/thread?tid=19b852cb0e23a0a5&hl=en Bug 25264 - Frames render correct in any other browser https://bugs.webkit.org/show_bug.cgi?id=25264
Attachments
Add attachment proposed patch, testcase, etc.
Anne van Kesteren
Comment 1 2023-12-30 05:01:25 PST
Not seeing this error anymore.
Note You need to log in before you can comment on or make changes to this bug.