W3C home > Mailing lists > Public > public-html@w3.org > April 2008

Parsing: <noframes> before <frameset>

From: Simon Pieters <simonp@opera.com>
Date: Fri, 04 Apr 2008 16:55:21 +0200
To: "public-html@w3.org" <public-html@w3.org>
Message-ID: <op.t83c2jtyidj3kv@zcorpandell.palace.opera.no>

http://www.zercom.nl has a <noframes> element before the <frameset>.

    http://parsetree.validator.nu/?doc=http%3A%2F%2Fwww.zercom.nl&submit=Print+Tree
    http://james.html5.org/cgi-bin/parsetree/parsetree.py?uri=http%3A%2F%2Fwww.zercom.nl

HTML5 says to put the <noframes> in <body> and then drop the <frameset>.  
Our current implementation is like HTML5 but it broke the above site, so  
we'll revert to not drop the <frameset>.

    http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%3Cnoframes%3Exxx%3C%2Fnoframes%3E%3Cframeset%3E
    http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%3Chead%3E%3Cnoframes%3Exxx%3C%2Fnoframes%3E%3Cframeset%3E
    http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%3Chead%3E%3C%2Fhead%3E%3Cnoframes%3Exxx%3C%2Fnoframes%3E%3Cframeset%3E

IE puts the <noframes> element in <head>.

Safari doesn't create a <head> for the first, creates a <head> and a <body  
style='display:none'> for the second (huh?), and puts the <noframes> after  
<head> for the third.

Firefox puts the <noframes> after <head>.

Opera 9.5b1 doesn't create a <head> for the first and puts <noframes>  
after <head> for the second and third.


I would suggest to either align with IE or Firefox (i.e., put the  
<noframes> in <head> or after <head>). The important thing here is that  
the <frameset> must not be dropped when <noframes> comes before it.

-- 
Simon Pieters
Opera Software
Received on Friday, 4 April 2008 14:56:13 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:54 UTC