Question: I am getting some peculiar behavior in Firefox with localForage. I set up a page to load two arrays using the standard 'setItem' form:

```
 <script src="localforage.js"></script>
 <body>
<script>
var data = [1,2,3,4,5];
localforage.setItem("saveData", data, function(err, value) {
if (err) {
 console.error('error: ', err);
} else {    
console.log("Data Saved");
}});

localforage.getItem("saveData", function (err, value) {
if (err) {
   console.error('error: ', err);
} else {
    console.log('saveData is: ', value);
    localforage.keys(function(err, keys) {
    console.log("Keys: " + keys);
    console.log("Number of keys: " + keys.length);
    });
}});
</script>
</body>
</html>

```

The array was saved correctly.

I then made a second page, using exactly the same "getItem" function.

In Chrome, the data showed up, but in Firefox it was not listed at all, and could not be opened. 

Has anyone else experienced this? In Firefox, even opening the second page in the same session fails to find the saved file. I have tried changing security.fileuri.strict\_origin\_policy, but it made no difference.

I would rather use Firefox, but I can't if it keeps losing saved data.

Answer: 
I also had the same issue but solved it after some researching, trials and discussions. Extensions like FireStorage Plus! and simple session storage do not work flawlessly for detecting this data, especially if it is being performed on a page/file other than the original root page/file.

The solution for me was to use the native FF Storage Inspector. Only then could I see ALL of the data I was missing. Those extensions did not show the data, even though it was being set.

Refer to: [localForage setItem/getItem unreliable in Firefox / FireStorage Plus](https://stackoverflow.com/questions/36482778/localforage-setitem-getitem-unreliable-in-firefox-firestorage-plus)

[![enter image description here](https://i.stack.imgur.com/LRGwz.png)](https://i.stack.imgur.com/LRGwz.png)

In addition, **for future assistance with localForage issues, try their IRC chat** **#localforage** at <https://webchat.freenode.net/> and look for **tofumatt**. He is the guru you want to confer with. ^5
Are you testing this from `file://` as opposed to `http://`? I believe in Firefox you cannot access IndexedDB if you open an HTML page from `file://`. So in this case you would need to run an HTTP server – easiest way is to do `python -m SimpleHTTPServer 8080` and then go to `http://localhost:8080`. Chrome might be different.