>> It creates consistent browser behavior despite tag soup. Agreed. >> The mistake XML made may have been attempting to fix authors instead of browsers. Hehe. :) -Mike -----Original Message----- From: www-tag-request@w3.org [mailto:www-tag-request@w3.org] On Behalf Of Elliotte Harold Sent: Thursday, November 02, 2006 11:09 AM To: Bjoern Hoehrmann Cc: www-tag@w3.org Subject: Re: New TAG issue: TagSoupIntegration-54 Bjoern Hoehrmann wrote: > I consider that unacceptable. Besides, why would this transformation > be applied only to "tag soup" and not to application/xhtml+xml resources? So what would you do instead? The status quo is *worse* than this. > Putting some tag soup parsing algorithm in some specification takes us > back absolutely nowhere. I disagree. It creates consistent browser behavior despite tag soup. The mistake XML made may have been attempting to fix authors instead of browsers. -- Elliotte Rusty Harold elharo@metalab.unc.edu Java I/O 2nd Edition Just Published! http://www.cafeaulait.org/books/javaio2/ http://www.amazon.com/exec/obidos/ISBN=0596527500/ref=nosim/cafeaulaitA/Received on Friday, 3 November 2006 13:37:52 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 12 September 2008 07:02:13 GMT