Lists Home |
Date Index |
It isn't a data island. It is non-HTML in the renderer.
To be specific, it is VML inside HTML using the CSS behavior
support and the xmlns declaration, per the manual.
What happened was a comment became denested (missing end
comment decl) and was not noticed because the values for
the VML were hardwired, so the rendering looked ok. While
adding a feature, it became apparent that something wasn't
right with the original. The missing end comment decl
was picked up by a later comment and that effectively
commented out the good code. So a bug was acting like a
feature in the instance. NBFD, I can fix these but it
occurred to me that the VML was malformed and the
browser didn't gripe about it. So I thought, sure
it's inside the HTML but it really isn't. (is
namespaced markup actually inside markup with a
different namespace; not really).
Then it occurred to me the browser doesn't actually
know the difference if it isn't in an XML document.
I dunno Joshua. It seems to me that grandfathering
HTML leads to problems worse than actually creating
an XML browser that knows it is one. My particular
bug is fixable, but it tells me that when using
XML inside non-XML, I can't trust rules I thought
I could trust. It should know that the VML is an
XML app, but wow... it hurts my brain to think
about how that would work while still grandfathering
HTML tag stacking.
From: Dare Obasanjo [mailto:email@example.com]
> > The subject says it. If HTML has an XML
> > namespace inside it, is the Draconian parse rule still in effect?
> Exactly how do you embed XML inside HTML let alone just XML
By the way I do know you can do this in an IE specific manner using XML
data islands but I'd assumed this was non-standard and unsupported in