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

Re: [XHR2] Disable new response types for sync XHR in Window context

From: Anne van Kesteren <annevk@opera.com>
Date: Mon, 14 Nov 2011 14:30:53 +0100
To: "Webapps WG" <public-webapps@w3.org>, "Olli Pettay" <Olli.Pettay@helsinki.fi>, olli@pettay.fi
Message-ID: <op.v4xuhrnl64w2qv@annevk-macbookpro.local>
On Fri, 11 Nov 2011 20:03:53 +0100, Olli Pettay <Olli.Pettay@helsinki.fi>  
wrote:
> I think we should strongly encourage web devs to move away from
> sync XHR (in Window context, not in Workers). It is bad for UI
> responsiveness.
>
> Unfortunately sync XHR has been used quite often with the old
> text/xml types. But maybe we could disable sync XHR for the new
> types, and also make .response to throw if it is used with
> sync XHR.
>
> Comments?

I think we could make responseType throw "InvalidAccessError" (currently  
response never throws, would be nice to keep that), but we just changed  
responseType so you can set it before invoking open().

We could of course do that if you set responseType during UNSENT open()  
will throw "InvalidAccessError" if you set async to false.

Should we do this for any features? E.g. cross-origin requests? If you  
pass user/password for cross-origin requests open() is already supposed to  
throw.


> http://www.w3.org/Bugs/Public/show_bug.cgi?id=14773
> https://bugzilla.mozilla.org/show_bug.cgi?id=701787
> https://bugs.webkit.org/show_bug.cgi?id=72154


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Monday, 14 November 2011 13:31:44 GMT

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