- From: Henri Sivonen <hsivonen@iki.fi>
- Date: Fri, 7 Dec 2007 09:45:53 +0200
- To: Sam Ruby <rubys@us.ibm.com>
- Cc: Ian Hickson <ian@hixie.ch>, public-html <public-html@w3.org>
On Dec 7, 2007, at 02:51, Sam Ruby wrote: > Thought experiment: I realize that it is against the tradition of > HTML1 through HTML4, but what would break if *all* content model > restrictions that deal with the distinction between block and inline > elements were dropped? Could specific restrictions then be added > back in which address specific problems (either of ambiguity or of > interoperability)? [...] > The mistake I had made was of the form > > <ul> > <li><p>text</p></li> > <li><p>text</p></li> > <li><p>text</p></li> > <p>text</p> > <p>text</p> > </ul> > > This clearly is bogus, and I'm glad that the conformance checker > flagged it. The fix was to move the final </li> to after the final > </p>. In XHTML5, your example parses unambiguously and does not cause interop problems in top 3 browsers that support XHTML. Yet, intuitively, it is clearly bogus. This suggests that the implicit line isn't quite at ambiguity or interop problems. -- Henri Sivonen hsivonen@iki.fi http://hsivonen.iki.fi/
Received on Friday, 7 December 2007 07:46:05 UTC