W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2014

Re: =[xhr]

From: Brian Kardell <bkardell@gmail.com>
Date: Fri, 1 Aug 2014 10:13:53 -0400
Message-ID: <CADC=+jdCE53EevZ5Y8M-T6P+eNvoZtHGJSKoQu=tYokoid_zpA@mail.gmail.com>
To: nmork_consultant@cusa.canon.com
Cc: public-webapps@w3.org, "Tab Atkins Jr." <jackalmage@gmail.com>
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
Received on Friday, 1 August 2014 14:14:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:26 UTC