George Beckman a écrit : > Blank screen here. Firefox. Done at the bottom of the screen. I > allowed popup windows and no luck. > > Here is the html Firefox finds: > > <html> > <head> > <title>FB Reference</title> > <meta http-equiv="content-type" content="text/html;" /> > <meta name="AppleTitle" content="FBHelp" /> > <meta name="AppleIcon" content="../gfx/FB16.png" /> > <link href="res/fb.css" type="text/css" rel="styleSheet"> > </head> > <body> > <frameset cols="210,*"> > <frame src="fbindex.htm" name="index"> > <frame name="main"> > </frameset> > </body> > </html> > According to the HTLM validator in Firefox the code above is missing a DOCTYPE, therefore it is interpreted as HTML. Mixing HTML and XHTML syntaxes in that case is not a good practice that can trigger cascading problems with some browsers. Here are a few messages I got: The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid. …-type" content="text/html;charset=iso-8859-1" /> The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HMTL 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HMTL 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML. <meta name="AppleTitle" content="FBHelp" /> The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed). One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error). HTH Alain