- From: <bugzilla@jessica.w3.org>
- Date: Fri, 06 May 2011 16:12:34 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12620
Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Simetrical+w3cbug@gmail.com
--- Comment #1 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-05-06 16:12:33 UTC ---
localStorage is, unfortunately, *not* an asynchronous API. It's synchronous.
IndexedDB is being defined purely asynchronously to avoid the problem of
blocking the page's functioning.
As I understand it, the bigger issue here is just that it's not practical to
let every site in the world permanently use up dozens of megabytes of your disk
space. Browsers are planning to allow some way of permitting select sites to
use more storage, but they're not sure what good UI for it is, so that the user
can make an informed decision. Ideally they'd draw some judgment based on
things like how much disk space is available, how much the user visits the
site, things like that.
But you really have to talk to the browser implementers about this, not the
spec writers. The reason the spec says 5 MB is because implementers weren't
willing to commit to allowing all sites to use more than that. The spec
follows the implementations, not the other way around -- a spec is just a way
for implementers to coordinate, not something that can make them do something
they don't want to.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 6 May 2011 16:12:36 UTC