- From: Alexey Proskuryakov <ap-carbon@rambler.ru>
- Date: Tue, 21 Nov 2006 11:55:01 +0300
- To: Anne van Kesteren <annevk@opera.com>
- CC: "Web APIs WG (public)" <public-webapi@w3.org>
On 11/19/06 5:25 PM, "Anne van Kesteren" <annevk@opera.com> wrote: >> However, I'm not seeing this behavior in Firefox 2 - it seems to always >> encode sent documents as UTF-8. Is this something that has been already >> discussed, and decided in favor of the new behavior? I'm feeling >> somewhat reluctant to break Firefox compatibility (WebKit didn't support >> xmlEncoding before, and thus also encoded documents as UTF-8). > > I'm fine with always serializing to UTF-8 if that's what browsers do. One > less character encoding issue for authors to deal with. :-) There's one difference between WebKit and Firefox in this regard, however. WebKit serializes the document without any XML declaration, so encoding as UTF-8 is only natural. However, Firefox includes a declaration, with an encoding that doesn't match the actual one - which looks like a bug to me. Perhaps, the requrement could be that the document should be encoded to be valid - i.e. if an XML declaration is present, it should match the actual encoding? - WBR, Alexey Proskuryakov
Received on Tuesday, 21 November 2006 08:56:04 UTC