W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2010

[whatwg] Character encoding of document.open()ed documents

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 01 Apr 2010 23:11:50 -0400
Message-ID: <4BB56076.6090905@mit.edu>
On 4/1/10 9:29 AM, Henri Sivonen wrote:
> On Mar 31, 2010, at 16:24, Boris Zbarsky wrote:
>
>> I distinctly recall Gecko having compat bugs of various sorts here
>> for the external resource case at one point (as in, people
>> reporting intranet apps and the like that worked in IE but not
>> Gecko), and us trying pretty hard to fix them.
>
> Could this have been only about trying to decode the external
> resources as UTF-16 vs. trying to decode them using any ASCII
> superset encoding?

It's possible.  It's been a while since I last looked at this code...

> By looking at CVS blame a second time, I found only
> https://bugzilla.mozilla.org/show_bug.cgi?id=255820 where the key
> thing seems to be avoiding UTF-16 and not so much letting the meta
> have an effect

That's the bug I was largely thinking of, yes.

So maybe we're ok with UTF-8.

-Boris
Received on Thursday, 1 April 2010 20:11:50 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:22 UTC