On Fri, 04 Sep 2009 13:21:54 +0200, Stefan Behnel wrote:
Not a bug in IE (this time), which is correctly parsing the file as html.
>>> ... which is obviously not the correct thing to do when it's XHTML.
>>
>> It isn't though; it's HTML with a XHTML DOCTYPE
>
> Not the page I look at (i.e. t
Richard Brodie wrote:
> "Stefan Behnel" wrote:
>> Lee wrote:
>>> Not a bug in IE (this time), which is correctly parsing the file as html.
>> ... which is obviously not the correct thing to do when it's XHTML.
>
> It isn't though; it's HTML with a XHTML DOCTYPE
Not the page I look at (i.e. the li
"Stefan Behnel" wrote in message
news:4aa01462$0$31340$9b4e6...@newsspool4.arcor-online.net...
>>Not a bug in IE (this time), which is correctly parsing the file as html.
>
> ... which is obviously not the correct thing to do when it's XHTML.
It isn't though; it's HTML with a XHTML DOCTYPE, a
basically any tag that can
have content in html you had better close the html way (),
or IE will see it as unclosed and will not display the rest of the
page after the tag (or do something else unexpected). Not a bug in IE
(this time), which is correctly parsing the file as html.
... which is ob
Lee wrote:
> basically any tag that can
> have content in html you had better close the html way (),
> or IE will see it as unclosed and will not display the rest of the
> page after the tag (or do something else unexpected). Not a bug in IE
> (this time), which is correctly parsing the file as htm
I went with a space, but a comment is a better idea.
I only mention the
I went with a space, but a comment is a better idea.
I only mention the
Lee wrote:
> Elementtree (python xml parser) will transform markup like
>
>
>
> into
>
>
>
> which is a reasonable thing to do for xml (called minimization, I
> think).
>
> But this caused an obscure problem when I used it to create the xhtml
> parts of my website,
> causing Internet Explore
