- From: Henri Sivonen <hsivonen@iki.fi>
- Date: Fri, 30 Sep 2011 15:40:09 +0300
- To: public-webapps@w3.org
On Fri, Sep 30, 2011 at 3:35 PM, Anne van Kesteren <annevk@opera.com> wrote: > On Fri, 30 Sep 2011 14:29:32 +0200, Henri Sivonen <hsivonen@iki.fi> wrote: >> >> On Fri, Sep 30, 2011 at 3:04 PM, Anne van Kesteren <annevk@opera.com> >> wrote: >>> >>> I do not see why "text" and "moz-chunked-text" have to be the same. >>> Surely we do not want XML encoding detection to kick in for chunks. >> >> Does "text" and default need to be the same for responseText for >> text/html and XML types? It seems annoying to have to run the <meta> >> prescan or to run the XML declaration detection without running a full >> parse in the "text" mode. > > Unless we disable responseText and responseXML when responseType is not the > empty string I am not sure that makes sense. responseType is a newish feature. If it's OK for responseType == "chunked-text" to use encoding determination rules that differ from responseType == "" or responseType == "document", why should responseType == "text" have to be consistent with responseType == "" instead of being consistent with responseType == "chunked-text"? -- Henri Sivonen hsivonen@iki.fi http://hsivonen.iki.fi/
Received on Friday, 30 September 2011 12:40:47 UTC