• From: David Carlisle <davidc@n...>
• To: James Clark <jjc@j...>
• Date: Wed, 15 Dec 2010 09:54:19 +0000

On 15/12/2010 09:32, James Clark wrote:

> It turns out that they do not.  HTML5 says that the error recovery for
> <br></br>
> is to treat it as
> <br><br>
> (I find this bizarre in the extreme.)

Basically it just tries to formalize existing browser parsing bugs.

> The spec is hard to read but you
> can see it in
>
> http://dev.w3.org/html5/spec/tokenization.html#parsing-main-inbody
>
>     An end tag whose tag name is "br"
>
>     Parse error. Act as if a start tag token with the tag name "br" had
>     been seen. Ignore the end tag token.

Note that is _only_ for br (as far as I can see) other void elements 
such as hr and img have a different recovery behaviour, and ignore the 
end tag.

>
>
> There is a handy tool for seeing how the HTML5 spec recovers from errors:
> http://software.hixie.ch/utilities/js/live-dom-viewer/
>
> James
>

yes although note you need to be using a browser that implements the 
html5 parser, hixie's dom viewer shows what dom your browser created 
rather than the dom the html5 spec specifies, or to get a different view 
of the same information you can (in firefox 4 at least) just select the 
document (or a fragment of the document) and view selection source from 
the right mouse menu option. Despite what it says it isn't really a 
source view it shows a linearisation of the relevant part of the dom.

David

________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.

This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. 
________________________________________________________________________

• References:
  • MicroXML
    • From: James Clark <jjc@j...>
  • Re: MicroXML
    • From: Henri Sivonen <hsivonen@i...>
  • Re: MicroXML
    • From: James Clark <jjc@j...>
  • Re: MicroXML
    • From: James Clark <jjc@j...>