- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Wed, 4 Jul 2012 11:21:41 +0200
- To: Jochen Eisinger <jochen@chromium.org>
- Cc: public-webapps@w3.org
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. -- http://annevankesteren.nl/
Received on Wednesday, 4 July 2012 09:22:10 UTC