Bug 34063 – fail to parse application/xhtml+xml files with encoding="iso-8859-1" and libxml2 >= 2.7.4

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: XML

[Vincent Lefevre]

Created attachment 47303 [details]
testcase

Webkit-based applications (midori, liferea, GtkLauncher) fail to parse XHTML files with encoding="iso-8859-1".

With the above URL (file also added as an attachment), under Linux (Debian) with libwebkit 1.1.19, I get:
  This page contains the following errors:
  error on line 2 at column 2: StartTag: invalid element name

and with a similar page (which validates with xmllint), under Mac OS X Tiger with Liferea and webkit-gtk 1.1.10, I get:
  This page contains the following errors:
  error on line 2 at column 2: Char 0x0 out of allowed range

(though there isn't such a character in the page).

There's no such problem with encoding="utf-8", e.g.
  http://www.vinc17.net/test/webkit-utf8.html

Note that these simplified examples contain only ASCII characters.

Also, I couldn't try with the latest nightly build (23 Jan) on my Mac OS X machine because it crashes immediately.

[Vincent Lefevre]

The bug occurs only when the file is served as application/xhtml+xml, not when it is served as text/html. That's bad because webkit declares to support application/xhtml+xml.

[Alexey Proskuryakov]

I cannot reproduce with Safari on Mac OS X.

[Vincent Lefevre]

I couldn't reproduce it either with Safari, but my machine is under Mac OS X Tiger, so that's quite old. Now, I wonder whether this is specific to GTK (but I don't see what GTK has to do with something related to the encoding or MIME type declaration).

Also I think that there were no such problems in the past (several months ago), but the bug still occurs with old Debian packages of midori and libwebkit-1.0-1.

[Alexey Proskuryakov]

Could be related to bug 30508.

[Vincent Lefevre]

(In reply to comment #4)
> Could be related to bug 30508.

Yes, the bug occurs with the libxml2 2.7.4.dfsg-1 Debian package, but not with 2.7.3.dfsg-2.1.

[Vincent Lefevre]

The patch fixing bug 30508 also fixes the problem I've reported. So, this is really a duplicate of bug 30508.

*** This bug has been marked as a duplicate of bug 30508 ***