[Webkit-unassigned] [Bug 66056] The XML parser doesn't ignore user's encoding choice for XML files

Sat Aug 13 12:53:02 PDT 2011

https://bugs.webkit.org/show_bug.cgi?id=66056

--- Comment #13 from Leif Halvard Silli <xn--mlform-iua at xn--mlform-iua.no>  2011-08-13 12:53:02 PST ---
(In reply to comment #8)
> That's a good point. Another thing is that an XML document may be in a subframe inside an HTML one.

Perhaps I misunderstood what you meant by this? At first I interpreted this as support of the solution I suggested - namely, to adhere to XML 1.0 encoding rules. But perhaps not?

So, to test, I produced the page you were talking about  - this HTML page is WINDOWS-1252 labelled  (originally it is UTF-8 encoded) with a polyglot XHTML subframe (hence it is UTF-8 encoded and it also includes the HTML charset declaration) :

        http://malform.no/testing/html5/bom/frame

BROWSER RESULTS:

* IE9 and Firefox: they treat the subframe as UTF-8 - thus respecting the encoding default, over both mother page's encoding and over the user's choice as well.

* Webkit: it lets the subframe inherit the encoding from the HTML page. (At the very least it respects the UTF-8 encoding if there is BOM.)

* Opera: behaves like Webkit (except that it doesn't even respect the BOM)

* IE8 and below sniffs it as HTML, and also respect the HTML encoding declaration. (If I drop the encoding declaration, then it defaults to WINDOWS-1251.

If you ask me, this is a big failure for Webkit and Opera, in every way. Completely illogical behaviour.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.