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

Quota Management API error codes

From: Jochen Eisinger <jochen@chromium.org>
Date: Tue, 3 Jul 2012 14:56:33 +0200
Message-ID: <CALjhuievq+gax_PUP5GEhHW6WOBfzW8d+G4AtQmKiXaR4XCKTA@mail.gmail.com>
To: public-webapps@w3.org

while reading http://www.w3.org/TR/quota-api/#quota-handling-in-storage-apiI
wondered what the desired behavior was when the UA refuses to grant
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

Received on Wednesday, 4 July 2012 06:57:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 13:55:51 UTC