- From: Adam Barth <w3c@adambarth.com>
- Date: Wed, 31 Dec 2008 11:30:04 -0800
- To: "Philip Taylor" <pjt47@cam.ac.uk>
- Cc: "Jonas Sicking" <jonas@sicking.cc>, public-html@w3.org, "Julian Reschke" <julian.reschke@gmx.de>
On Tue, Dec 30, 2008 at 4:57 PM, Philip Taylor <pjt47@cam.ac.uk> wrote: > http://www.haliburtonrealestate.on.ca/ -- <li><a href="http://www.mls.ca" > target="_blank" title="Multiple Listing Service" />MLS</a> > > http://www.ccitula.ru/ -- <a href="pages/virtv.htm"/> <img > src=http://www.ruschamber.net/banner/VEru158x50.jpg border=0></a> > > http://takasago.shop-pro.jp/ -- <a href="?pid=1912944" /><img > src="http://img05.shop-pro.jp/PA01015/854/product/1912944_th.jpg" > class="border" /></a> > > http://www.alternativegreetingcards.com/ -- <a href="products.asp?id=57" > class="submenu" />Wizard of Oz</a> I'm not an HTML parsing expert, but these examples seem as easy to fix up as other parsing oddities like mis-nested tags (e.g., <b>foo<i>bar</b>baz</i>). Why can't the parser assume that <foo /> is a void element until it finds a </foo> that would otherwise close the tag? This would permit forward and backward compatible parsing and ease of authoring. Adam
Received on Wednesday, 31 December 2008 19:30:46 UTC