Sorry to hear that :/ I'm eagerly waiting for the Storage API to be implemented in all browsers, so we can do away with all the persistent storage issues.

Before working on this I'd like to see at least one other browser (Firefox) ship the API, and I also need to complete the migration over to HTTPS (Chrome only enables navigator.storage in secure contexts), which is a tricky beast because IndexedDB data is per-origin (i.e. not shared between HTTP and HTTPS), so users will need to migrate their data. Once this done, this feature will be top of my list.

@Thibaut I thought devdocs was already https-enabled? #446

I just switched from http to https and it kept all my settings. 😕

@jayandcatchfire While DevDocs works over HTTPS, HTTP is still the default (one reason being that until #633, many docs had insecure assets/images which wouldn't load over HTTPS) . Most people use the HTTP version.

Before implementing persistent storage, I want to force HTTPS, so that the feature is available to everyone. However, forcing HTTPS will nuke all HTTP users' offline data (but not their settings—like you said), so before doing that I need to implement a few things to let the users know and ease the transition.

About the HTTP => HTTPS migration in order to minimize data loss for users I think (once HTTPS is ready to deploy of course) there should be a big notice displayed warning them that due to protocol migration, there data will be lost.
We should guide them with an export / import procedure to help them. Maybe should we discuss this point in an other issue ?

@Kaijiro I've made a ticket about that: #823