W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2005

[whatwg] <p> elements containing other block-level elements

From: Henri Sivonen <hsivonen@iki.fi>
Date: Tue, 12 Apr 2005 14:37:16 +0300
Message-ID: <09517b62913cebc85107df48f71fddcf@iki.fi>
On Apr 12, 2005, at 12:31, Ian Hickson wrote:

> Many people feel that a minor typo in their document should not cause
> their page to stop rendering altogether. I have spoken with a _lot_ of
> authors who really do not like XML's draconian error handling, 
> including
> many authors who are always ensuring their documents are valid.

Recently, I made a typo and left out the slash in an end tag (on the 
tag soup side). Since Gecko forces tag soup into a tree, I didn't 
notice anything in Firefox. However, in IE my script produced 
exceedingly weird results. It turned out that IE had created a non-tree 
DOM and my single typo had multiplied thanks to cloneNode preserving 
the non-treeness. It would have saved me debugging time if I had seen a 
parse error message up front.

> I myself have occasionally made typos and other mistakes that, if I had
> used XML, would have left my site unusable, without my knowledge, for
> several hours at a time.

 From the "tools will save us" point of view, you need a text editor 
that tries to parse the doc using an XML parser when you intend to 
write XML.

Henri Sivonen
hsivonen at iki.fi
Received on Tuesday, 12 April 2005 04:37:16 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:40 UTC