Is there any plan for involving the user in storage allocation decisions for
IndexedDB? [1]
For comparison, the WebStorage API [2] doesn't have any special support for
the user to make allocation choices. My understanding is that browsers have
a fixed storage limit per origin -- in Chromium, 5Mb
On Tue, Apr 13, 2010 at 4:53 PM, João Eiras jo...@opera.com wrote:
On Tue, 13 Apr 2010 12:09:14 +0200, Mark Seaborn mseab...@chromium.org
wrote:
Is there any plan for involving the user in storage allocation decisions
for
IndexedDB? [1]
For comparison, the WebStorage API [2] doesn't have
On Tue, Apr 20, 2010 at 7:17 PM, Shawn Wilsher sdwi...@mozilla.com wrote:
On 4/20/2010 4:11 AM, Mark Seaborn wrote:
1) It doesn't allow a web app to ask for a storage allocation up front,
before it starts to consume the storage.
Why does that matter?
It doesn't support the use cases
On Thu, Jun 10, 2010 at 10:04 AM, Jonas Sicking jo...@sicking.cc wrote:
For what it's worth, it's unlikely that we at mozilla will implement
this anytime soon, if at all. We're currently working on trying to
reduce the ability to fingerprint [1] and this would be a step in the
wrong direction
On Wed, Jun 2, 2010 at 5:06 PM, Jian Li jia...@chromium.org wrote:
I have one question regarding the scheme for Blob.url. The latest spec says
that The proposed URL scheme is filedata:. Mozilla already ships with
moz-filedata:. Since the URL is now part of the Blob and it could be used
to
