Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by grun | Hacker News Reader

Parent Full thread

grun·

Clearing cookies is a common user action. Even for relatively non-technical users.

And under storage pressure, browsers evict data stored in IndexedDB, LocalStorage, and/or SessionStorage. See

https://developers.google.com/web/fundamentals/instant-and-o...

IronDB is resilient in the face of such events.

Thank you for your feedback. I'll add an explanation about such in the documentation.

View on HN

If anyone could point to an up to date docs around storage eviction in browsers it would be greatly appreciated. It's been a big hit to our team's confidence in the "use the platform" mentality that this is not accurately documented.

I remember reading a 5MB limit some place (ages ago) and I'm not able to find the reference at the time.

My team has been assuming that is true (for local,session)Storage and so far haven't been bitten.

Only occasionally have we even gotten close to that size. You can also shove loads of data in the DOM.

Edit: one of the old refs - 10MB

https://www.html5rocks.com/en/tutorials/offline/quota-resear...

That's the answer I was looking for, thanks. The intuition I have is that if someone deletes something from localStorage (or clears localStorage altogether), they want that data gone.

Those docs are dated unfortunately. For example, in my tests on multiple android devices and Mac OS the storage limit on Chrome is closer to 20% of total disk size and you don't need to prompt the user for persistent storage like you prompt for access to gps.

What about https://developers.google.com/web/updates/2016/06/persistent...

Persistent storage requires explicit user permission.

IronDB doesn't.

See https://developers.google.com/web/updates/2016/06/persistent....

Great point, though. I'll highlight this in the documentation. Thank you.

Reply on news.ycombinator.com