BTW, not sure if you have this in the WhatWG parsing spec, but a
stray </p> (that does not match some opening <p>) has to be treated
like an open <p>.
Also, <script src="..."/> is actually supported even in HTML by
Firefox and Safari. We're stuck with it forever as well, since most
of the Dashboard widgets use <script src="..."/> in HTML. It isn't
understood by WinIE or Opera though. You can say we're wrong in the
spec, but we won't be able to change it. :(
dave
([EMAIL PROTECTED])
On Feb 15, 2006, at 4:16 PM, Ian Hickson wrote:
On Wed, 15 Feb 2006, Michael Enright wrote:
What about '<foo />' with a space between 'o' and '/' ? There are
many
"legacy" pages with that kind of mark-up on <br> elements and so
forth.
There are also lot of legacy pages that do it on things like <p>,
sadly.
On <br> it's harmless, and it doesn't help either way to say that it
makes an empty element, since it's empty anyway. On other elements, it
makes HTML5 UAs have a different DOM that legacy UAs.
--
Ian Hickson U+1047E )
\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _
\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--
(,_..'`-.;.'
