5

There are several discussions on the web about technical details of how iOS 6 introduced a pain in the butt problem for us developer that when Safari's private mode is on, then the browser's LocalStorage is not writable.

But how are you dealing with this in your modern web application? Do you just detect this and notify the user via a modal window notification that your web application is not usable unless the user disables Safari's private mode? Or have you implemented fallback measures that don't use LocalStorage at all? If so, which measures are those?

Paul Sweatte
  • 24,148
  • 7
  • 127
  • 265
ux.engineer
  • 10,082
  • 13
  • 67
  • 112

1 Answers1

4

Unfortunately, the only away around it is to fail silently (wrap a dummy set/get to localStorage in a try/catch) and gracefully degrade.

There are several other storage techniques you can use to gracefully degrade, e.g., cookies. There are also several libraries which have already solved this. Here's an example reference post for more info: HTML5 Local Storage fallback solutions.

Community
  • 1
  • 1
joeltine
  • 1,610
  • 17
  • 23
  • Thanks, this solved the question! Actually I have had AmplifyJS in mind but today I had forgot it or had assumed it would have been based only on LocalStorage. – ux.engineer Aug 09 '14 at 11:36