W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2003

Re: Can Browsers Attempt to Render Broken XHTML?

From: David Woolley <david@djwhome.demon.co.uk>
Date: Thu, 26 Jun 2003 22:43:39 +0100 (BST)
Message-Id: <200306262143.h5QLhdX03985@djwhome.demon.co.uk>
To: w3c-wai-ig@w3.org

> <select name=color>
>  <option>blue
>  <option>red
> </select>
> 
> works fine in most browsers, in a document declared as HTML. 
> If the document is declared as XHTML, you should use:

It should work fine in ALL conformant HTML parsers, as it is
perfectly valid and unambiguous HTML; it has the same parse tree
as the the normalised example below.  It is not an example of sloppy
HTML.  Sloppy HTML would be: <b><p>Heading</p></b> (same as XHTML:
content model violation, and use of wrong markup for semantics);
<b><i>bold-italic</b></i> (tag soup - not properly nested); or
<html><body>, as seen in much HTML email (content model violation -
missing mandatory element; the missing element is <title>; the head
element is present but the tags have been omitted, as can be the
<html> and </html> tags).  (All my sloppy examples are commonly found
in the wild.)

> 
> <select name="color">
>  <option>blue</option>
>  <option>red</option>
> </select>
Received on Thursday, 26 June 2003 17:55:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:10 GMT