[whatwg] Storage quota introspection and modification
Tab Atkins Jr.
jackalmage at gmail.com
Thu Mar 11 13:42:33 PST 2010
2010/3/11 Mike Shaver <mike.shaver at gmail.com>:
> I think of an infobar as relatively innocuous, and a good balance of
> user awareness versus flow interruption, but I repeat my lack of
> interaction design credentials!
Mark Pilgrim is trying to make his book, Dive Into HTML5, an offline
app. In the current Firefox permissions UI, every single page pops up
an infobar. To get around this he'd have to redesign the book to
serve itself from a single html document. This is obviously
suboptimal; ideally he'd just be able to take the existing book in
HTML format, add a manifest declaration, and be done with it. This
sort of usage is small enough that users shouldn't *need* even the
peripheral awareness of an infobar - it's nothing more than a small
cache, which Mark would like to provide as a convenience. Ideally
this would be totally invisible to the user unless they purposely try
and manage sites' offline storage, just as cookies currently work.
More information about the whatwg