Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Just had the issue yesterday, that I could not log in via Safari browser.
Safari 5.1.2.

I tried to log in via stack exchange and got following error:

QUOTA_EXCEEDED_ERR: DOM Exception 22: An attempt was made to add something to storage that exceeded the quota.
share|improve this question
I don't think that's Safari related necessarily - it's because the scripts don't gracefully handle an add-to-local-storage failure. But maybe it's easiest to reproduce in Safari. (BTW have you deliberately set a very low local storage limit, or is that default behaviour? And is this Safari on Windows or Mac? I know they ought to be the same but I've seen rendering bugs on Windows but not Mac.) – Rup Feb 22 '12 at 15:08
it is safari on mac. i just checked safari under windows, there it works... safari is default behaviour... it was just driving me crazy two days ago because i was started to think i m too stupid to log in :D ok, maybe it s only a bug at my machine. just wanted to report! thanks for tips – longilong Feb 22 '12 at 15:29
No, it is something that should be fixed: they need to catch exceptions from window.localStorage.setItem() and probably just ignore them. (Or remember the failure and don't try to do it again, but ignore is easiest.) – Rup Feb 22 '12 at 15:52
It works for me with Safari 5.1.3. I tried logging out, and in, on this very site, and I didn't get any error message. – kiamlaluno Feb 22 '12 at 17:12
up vote 4 down vote accepted

This will be fixed in the next build, Apple does something a little funny in privacy mode here...instead of saying "we don't support window.localStorage", it just throws an error when you try to call setItem on it. IMO this is bad behavior, but it's how Safari (on the iPad at least) works.

We'll trap and ignore that error just not remembering what you logged in with in these cases after the next build.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .