W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2010

Re: XHR LC comment: header encoding

From: Anne van Kesteren <annevk@opera.com>
Date: Sun, 31 Jan 2010 13:38:00 +0100
To: "Boris Zbarsky" <bzbarsky@mit.edu>
Cc: "Jonas Sicking" <jonas@sicking.cc>, "Julian Reschke" <julian.reschke@gmx.de>, "WebApps WG" <public-webapps@w3.org>
Message-ID: <op.u7eddmao64w2qv@annevk-t60>
On Tue, 05 Jan 2010 13:49:55 +0100, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> Apart from the obvious worry of switching away from a behavior that the  
> vast majority of UAs currently implement, with the ensuing potential for  
> website breakage, sounds fine...

I know... Though Opera not having received bug reports so far on this  
issue gives me some hope, since we have received lots of other bug reports  
on far more minor details starting very early on.

The editor drafts of XHR1 and XHR2 now include the change. This also moved  
things away from being defined in Unicode to a combination of bytes and  
ASCII. Please let me know if you (i.e. anyone reading this thread) have  
any editorial suggestions on my changes or if I missed something while  
making the edits.

Specifically search for "inflate" and "deflate" throughout the drafts:

   http://dev.w3.org/2006/webapi/XMLHttpRequest/
   http://dev.w3.org/2006/webapi/XMLHttpRequest-2/

Or review the diff of xhr-source:

   http://dev.w3.org/cvsweb/2006/webapi/XMLHttpRequest-2/xhr-source.diff?r1=1.6&r2=1.7&f=h

Kind regards,


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Sunday, 31 January 2010 12:38:39 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:36 GMT