Specification: http://dev.w3.org/html5/webstorage/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top
Referrer: 

Comment:
From James Vickers
james@metabench.com

I'm working on an HTML5 media player, it plays an album, in MP3 or OGG format.
In order to make a web app that's as functional as a native app, it would be
best to store the tracks locally. Localstorage logically seems like the place
to do this, but then there is the suggestion: 'A mostly arbitrary limit of
five megabytes per origin is suggested.'

That limit is far too low for my purpose. I suggest that either this, or a
different storage mechanism, allow provisioning of a much larger amount of
space, should the user agree, of up to 4GB (or even better 256GB). The issue
of a malicious app using up all the storage space is a real one, but HTML apps
being able to use very large storage areas would enable very useful apps and
overcome a current disadvantage of the web platform when compared to more
direct filesystem access. I suggest that the requirement to easily allow a
very large amount of space to be allocated for local storage, should the user
permit it, be put into the HTML spec. A clear dialog box could be specified
that says they are being asked if they want to allocate:

s    MB / GB of storage
n1   % of the total space
n2%  of the remaining space on the device
(n3%  of the remaining free space on the logical drive) optional

It could illustrate this with a pie chart and warn if the app is asking to
allocate a large amount of space.

The OS should enable easy viewing of what is taking up the space, similar to
how it illustrates the space taken by native apps.

This way the user could make an informed decision about allowing an app to use
a considerable chunk of the available space.

Posted from: 86.8.129.230
User agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.131 Safari/537.36