W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: [XHR2] responseText for text/html before the encoding has stabilized

From: Anne van Kesteren <annevk@opera.com>
Date: Sat, 01 Oct 2011 09:17:46 +0200
To: "Ian Hickson" <ian@hixie.ch>
Cc: public-webapps@w3.org, "Henri Sivonen" <hsivonen@iki.fi>
Message-ID: <op.v2nvvwfi64w2qv@annevk-macbookpro.local>
On Fri, 30 Sep 2011 20:05:41 +0200, Ian Hickson <ian@hixie.ch> wrote:
> I agree that the reloading alternative is even worse. What about just
> relying on the Content-Type charset="" and defaulting to UTF-8 if it  
> isn't there, and not doing any in-page stuff?

That would work for me. It seems Jonas is somewhat more concerned about  
legacy content not working well in that case, but the world is moving fast  
to UTF-8. (I think we should observe the BOM by the way as XMLHttpRequest  
already does.)

> How is the encoding determined for, e.g., text/plain or text/css files
> brought down through XHR and viewed through responseText?

Like the above.

Anne van Kesteren
Received on Saturday, 1 October 2011 07:18:33 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:36 UTC