Re: [w3c/ServiceWorker] Handle the quota exceeded error globally (#971)

> What's painful about it? Give that there may be other reasons for storage methods to fail, would we be saving much by having a global event for this?

I'm not sure about others. But my app was designed to use `Cache API` as a replacement for browser cache. So I use it pretty much everywhere in my app. Catching errors of every single write operations is quite painful to me. I actually expect a global event fired when the storage quota is exceeded, so that I can show some recommendations to users.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/971#issuecomment-246709939