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

2011-11-16 Thread Anne van Kesteren
On Tue, 15 Nov 2011 20:33:38 +0100, Jonas Sicking jo...@sicking.cc wrote: So if I understand the proposal correctly: After .open has been called with async=false: * setting .responseType to anything other than throws InvalidAccessError * setting .wirthCredentials to true throws

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

2011-11-16 Thread Matt Shulman
I sometimes like to write code in the window context (where debugging support is much better) before moving it to a web worker, so it would be awkward if the sync options differed on xhr between the two. (Analogous to this - I remember once i was trying to use the new FileSystemSync API and during

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

2011-11-16 Thread Glenn Maynard
On Wed, Nov 16, 2011 at 11:10 AM, Matt Shulman mat...@google.com wrote: I sometimes like to write code in the window context (where debugging support is much better) before moving it to a web worker, so it would be awkward if the sync options differed on xhr between the two. (Analogous to

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

2011-11-16 Thread Matt Shulman
On Wed, Nov 16, 2011 at 8:20 AM, Glenn Maynard gl...@zewt.org wrote: On Wed, Nov 16, 2011 at 11:10 AM, Matt Shulman mat...@google.com wrote: I sometimes like to write code in the window context (where debugging support is much better) before moving it to a web worker, so it would be awkward

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

2011-11-15 Thread Anne van Kesteren
On Mon, 14 Nov 2011 17:55:25 +0100, Jonas Sicking jo...@sicking.cc wrote: 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

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

2011-11-15 Thread Jonas Sicking
On Tue, Nov 15, 2011 at 4:22 AM, Anne van Kesteren ann...@opera.com wrote: On Mon, 14 Nov 2011 17:55:25 +0100, Jonas Sicking jo...@sicking.cc wrote: Yes, I think cross-origin should not work with sync. That is currently the only synchronous communication mechanism cross origin. Without it a UA

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

2011-11-15 Thread Olli Pettay
On 11/15/2011 09:33 PM, Jonas Sicking wrote: On Tue, Nov 15, 2011 at 4:22 AM, Anne van Kesterenann...@opera.com wrote: On Mon, 14 Nov 2011 17:55:25 +0100, Jonas Sickingjo...@sicking.cc wrote: Yes, I think cross-origin should not work with sync. That is currently the only synchronous

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

2011-11-15 Thread Jonas Sicking
On Tue, Nov 15, 2011 at 11:41 AM, Olli Pettay olli.pet...@helsinki.fi wrote: On 11/15/2011 09:33 PM, Jonas Sicking wrote: On Tue, Nov 15, 2011 at 4:22 AM, Anne van Kesterenann...@opera.com  wrote: On Mon, 14 Nov 2011 17:55:25 +0100, Jonas Sickingjo...@sicking.cc  wrote: Yes, I think

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

2011-11-14 Thread Anne van Kesteren
On Fri, 11 Nov 2011 20:03:53 +0100, Olli Pettay olli.pet...@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

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

2011-11-11 Thread Olli Pettay
Hi all, 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