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

[bugzilla-daemon at webkit.org]

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





--- Comment #2 from Leif Halvard Silli <xn--mlform-iua at xn--mlform-iua.no>  2011-08-11 12:47:36 PST ---
(In reply to comment #1)
> What is the difference between this bug and bug 66055?

The XML 1.0 spec discerns between internal encoding declaration (including the UTF-8 default ) and accompanied (a.k.a. external) encoding declaration delivered together with file over the protocol or file system. And hence, the difference between the two bugs goes like this:

* Bug 66055 is about Webkit's failure to obey UTF-8  as the [internal] default encoding (over the user chosen encoding).
* Bug 66056 - this bug - is about Webkit's failure to let the accompanied external protocol take precedence (over the user chosen encoding).

I can see that from Webkit's point of view, the problem perhaps is one and the same: In both cases, Webkit listens to what the user specifies in the Text Encoding menu, rather than doing what the spec says. 

And: As long as the user does not touch the Text Encoding menu - but leaves it set to 'Default'/'Automatic', then Webkit does select the correct encoding - with one exception: If the page contains the BOM, then it ignores the HTTP charset=foo attribute (See bug 66084 for the XML parser. There is a related bug for the HTML parser as well - bug 66085.)

I think there should be separate bugs, but that bug 66055, bug 66056 as well as bug 66084 and bug bug 66085, should be seen together - perhaps they should be marked as depending on oneanother?

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