430415 - reports spurious XML parsing error when XHTML file is on local disk

Status: RESOLVED DUPLICATE of bug 418391

(Core :: DOM: HTML Parser, defect)

Description

[Mike Hommey [:glandium]]

This was reported on Iceweasel in Debian BTS.
This was with version 3.0b5, which has no code modification other than the name.
Copy/paste:

If I copy http://crustytoothpaste.ath.cx/~bmc/index.xhtml to the local
disk, and then view it using a file:/// URI, iceweasel reports an XML
parsing error.  It does not report an error if I view it using an HTTP
or HTTPS URI.  The file is, in fact, valid XML, XHTML 1.0 Transitional,
XHTML 1.0 Strict, and XHTML 1.1.  xmllint (using libxml2) has no problem
with it.  Obviously, the URI for the CSS file won't work on the local
disk, but that should not cause an XML parsing error.

I have restarted Iceweasel several times, including in safe mode; this
problem always reoccurs.  Clearing the cache did not help.  This problem
did not occur with Iceweasel 2.  This also seems to occur on other pages
on my website, which is all XHTML.

And a followup:
I just noticed that if I remove the link tags, the parsing error
disappears.  Also, if I remove all the link tags referring to
stylesheets (including alternate stylesheets), the error disappears.  If
I leave even one link tag referring to stylesheets, the error still
occurs.  Howver, if I specify a full URI on the stylesheets, the error
also disappears.

It looks like the parser considers the unavailablity of stylesheets a
fatal parsing error, which it isn't.

I also cannot fully qualify the URIs because Safari does not accept URIs
for stylesheets that refer to HTTPS when the site is HTTP, and Firefox
provides a warning (via an icon in the location bar) for stylesheets
that refer to HTTP when the site is HTTPS.

Comment 1

[Jesse Ruderman]

Already fixed in post-beta-5 builds :)