Re: text/html for xml extensions of XHTML

Ian Hickson <> wrote:

>> But does Mozilla call its xml parser for ?
> Nope. If it did, ...

I think the following are indicative of bugs in Mozilla and I think
others would agree with my belief that we should be less forgiving of
mistakes in XHTML documents then we have been with HTML documents. It is my
hope that browsers that understand XHTML will do their best to inform users
when it encounters an invalid or broken page.

See also the recent ALA article, "Forgiving Browsers Considered Harmful":

> it would render the page without any expanded
> character entity references, since Mozilla is not a validating parser
> and thus skips parsing the DTD and thus doesn't know what &nbsp;,
> &middot; and &copy; are.

Mozilla's XML parser should be smart enough to recognize the HTML DTDs and
thus expand these entities properly, even if it doesn't validate the page
(which I believe it should).

> Not to mention that it would end up ignoring
> the print-media specific section of the stylesheet, which uses
> uppercase element names and thus wouldn't match any of the lower case
> elements (line 138 of the first stylesheet),

This appears to be a mistake in the W3C's stylesheet. I have sent them an

> and it would use an
> unexpected background colour for the page because the stylesheet sets
> the background on <body> and not <html>, which in XHTML will result in
> a different rendering to the equivalent in HTML4 (same sheet, line 5).

I have not heard of this change before. Can you point me to the section of
the XHTML spec that defines this?

[ Aaron Swartz | | ]

Received on Tuesday, 1 May 2001 23:00:10 UTC