[Webkit-unassigned] [Bug 31791] localStorage quota exceeded

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=31791





--- Comment #5 from Jeremy Orlow <jorlow at chromium.org>  2009-11-25 21:08:05 PST ---
The spec's mentioning of 5mb is really just an example.  There's nothing too
special about 5mb.  I guess it could be a bit confusing if that means 5 million
characters in other browsers and not WebKit ones.  Can you confirm that other
browsers that are implementing quotas typically allow 5 million?

But my point is that the spec probably won't change.  And over time, it's going
to only become less transparent to app developers where their space is going. 
And I think that's unavoidable, so we should just embrace it now...but I don't
have to deal with this stuff on a day to day basis either.

As for encoding: I'm pretty sure Ian would say this is an implementational
detail and should not be spec'ed.  But you could always bring it up on whatwg.

I think the next step (if any) is for you to make a case on WebKit-dev that we
should either: use UTF-8 encoding in the DB (and use that in the accounting) o
raise the WebKit default quota.  Both would be easier to sell if other browsers
were allowing for 5 million chars before hitting the limits.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.