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: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 14 Nov 2011 08:55:25 -0800
Message-ID: <CA+c2ei9-iJ4fke2ETc=3bMypug7gU84U_2Awdzg7AYA_mpbVyA@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: Webapps WG <public-webapps@w3.org>, Olli Pettay <Olli.Pettay@helsinki.fi>, "olli@pettay.fi" <olli@pettay.fi>
On Monday, November 14, 2011, Anne van Kesteren <annevk@opera.com> wrote:
> On Fri, 11 Nov 2011 20:03:53 +0100, Olli Pettay <Olli.Pettay@helsinki.fi>
>> 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
>> 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

Yes, I think cross-origin should not work with sync. That is currently the
only synchronous communication mechanism cross origin. Without it a UA
could put up UI if it wants to explicitly allow users to control such

/ Jonas
Received on Monday, 14 November 2011 16:55:57 UTC

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