Rob, The reason that there is a <noframes><body></noframes> in my source is that it's a trick that enables me to hide the ISP banner ads, so that they don't get displayed to the user. When a browser sees the first <noframes><body>, it hides the embedded code up to the next </ noframes>.
If this were running on a non-ad based server, then of course I wouldn't use that trick. On Sep 17, 10:15 am, RobG <[EMAIL PROTECTED]> wrote: > On Sep 17, 8:58 pm, AwayBBL <[EMAIL PROTECTED]> wrote: > > > Ha Ha RobG, and I guess you are the markup-police? > > No, but given an attempted DOCTYPE of XHTML strict, the only reason > any content is displayed at all is because it is served as text/HTML > so browser error correction does its best to fix the mistakes. > > What should a browser to do with: > > - a body element inside a noframes element > - multiple body elements in one document > - a doctype declaration between body elements > - an HTML element after a body > > and so on. The W3C validator starts with: > > "Unable to Determine Parse Mode! > "It was not possible to reliably choose a parsing mode for this > document, because: > > " the MIME Media Type (text/html) can be used for XML or SGML > document types > " No known Document Type could be detected > " No XML declaration (e.g <?xml version="1.0"?>) could be found > at the beginning of the document. > " The validator is falling back to SGML mode." > > That's kinda serious. :-) > > -- > Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
