Re: =[xhr]

If you use your tab key, you will discover that you will need to disable 
all controls under your spinner to prevent user input completely.  Kind of 
a lot of work to get exactly the effect that sync requests do for you.

I find sync xmlhttprequests useful and you don't, it's clear.  But instead 
of recognizing this and doing something like saying "hm.  interesting, 
maybe there is a use for it," you have decided since you have no use for 
sync requests that no one should be using them.  I don't care to go 
through the effort of trying to write this application with async requests 
again, when I already have experienced the fact they don't give me the 
desired behavior.



From:   Brian Kardell <bkardell@gmail.com>
To:     nmork_consultant@cusa.canon.com, 
Cc:     public-webapps@w3.org, "Tab Atkins Jr." <jackalmage@gmail.com>
Date:   08/01/2014 07:13 AM
Subject:        Re: =[xhr]




On Aug 1, 2014 9:52 AM, <nmork_consultant@cusa.canon.com> wrote:
>
> Thank you for letting me know my input is not desired. 
>
As Tab said, you can visually and functionally lock user input in your tab 
and even provide a progress meter. Nothing you suggest is difficult with a 
sync xhr and promises, and it's less hostile.  How is this unreasonable?
>
> From:        "Tab Atkins Jr." <jackalmage@gmail.com> 
> To:        nmork_consultant@cusa.canon.com, 
> Cc:        public-webapps <public-webapps@w3.org> 
> Date:        08/01/2014 06:46 AM 
> Subject:        Re: =[xhr] 
> ________________________________
>
>
>
>
> On Aug 1, 2014 8:39 AM, <nmork_consultant@cusa.canon.com> wrote:
> >
> > Spinner is not sufficient.  All user activity must stop.  They can 
take  a coffee break if it takes too long.  Browser must be frozen and 
locked down completely.  No other options are desirable.  All tabs, menus, 
etc. must be frozen.  That is exactly the desired result.
>
> By "spinner", I also meant freezing other parts of the page as 
necessary, or obscuring them so they can't be clicked.
>
> Asking to freeze the rest of the browser is unnecessary and extremely 
user-hostile, and we don't support allowing content to do that.
>
> ~TJ