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

Re: Quota Management API error codes

From: Jochen Eisinger <jochen@chromium.org>
Date: Thu, 5 Jul 2012 13:08:28 +0200
Message-ID: <CALjhuiceQKnwvKN0=6xHjn62t2eE1z7-sNtbuW1bbpQcwNgDrQ@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: public-webapps@w3.org
On Wed, Jul 4, 2012 at 11:21 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Tue, Jul 3, 2012 at 2:56 PM, Jochen Eisinger <jochen@chromium.org>
> wrote:
> > while reading
> http://www.w3.org/TR/quota-api/#quota-handling-in-storage-api
> > I wondered what the desired behavior was when the UA refuses to grant any
> > quota? I think it would be nice to specify this in the standard.
> >
> > E.g. currently WebKit will throw a QuotaExceeded exception when a page
> tries
> > to write to DOM storage when DOM storage is disabled, while Firefox
> throws a
> > Security exception on any access to DOM storage. These inconsistencies
> make
> > it difficult for website authors to write apps that work when the user
> > configured the UA to disable certain APIs
>
> That should (and is) defined in the standards that use the storage
> (such as Web Storage) as it very much depends on the API what the
> right solution is.
>
>
Sorry for being unclear.

I would like to see the standard to include what happens when a page
requests quota using requestQuota, but the UA doesn't fulfill the request
because of some user configured policies (and not because it's just not
possible).

This would allow a web site to display a more sensible message to the user
(e.g. "please enable storage" vs "your harddrive seems to be full")

 -jochen


> --
> http://annevankesteren.nl/
>
Received on Thursday, 5 July 2012 11:09:16 GMT

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