Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

ie 10 localStorage.getItem returns error: more data is available

I'm using the localStorage in my web application to save al kinds of data. However this does not seem to work with internet explorer 10.

When i try to test this with:

localStorage.testItem = "testing"

it works fine, however when I try

localStorage.setItem('testItem', 'testing');

I get an error: More data available. What is going on here?

like image 362
TomDoes Avatar asked Oct 27 '14 16:10

TomDoes


People also ask

Does IE support localStorage?

IE also supports localStorage from IE8 but it does not support localStorage in IE7 and previous versions. Cookies are small text files stored by browsers allowing for a max of 4KB while with localStorage we can store Mbs of localStorage data.

How do I check localStorage data?

With the extension's background page open, just go to the developer tools by pressing F12, then go to the Application tab. In the Storage section expand Local Storage. After that, you'll see all your browser's local storage there.

Is localStorage always available?

localStorage is a property that allows JavaScript sites and apps to save key-value pairs in a web browser with no expiration date. This means the data stored in the browser will persist even after the browser window is closed.


1 Answers

I don't have a solid answer for this, but I've been debugging this error on a remote user's box for about a month. I haven't had direct access to the box, but what I do know is:

  1. in my particular case, any reference to localStorage caused the "SCRIPT234: More data is available" exception. This is slightly different than the OP's problem
  2. Error 234: More data is available is a low-level Windows system error
  3. It doesn't matter whether "Enable DOM Storage" is checked inside "Tools / Internet options / Advanced / Security / Enable DOM Storage", the error happens both ways
  4. It happened in a very recent build of IE 11: IE 11.0.9600.17501
  5. There is no record of this error ever happening inside IE except for this SO question. It's typically a system-level error. The fact that it's bubbled up into the JS console is troubling. Usually when an OS reveals its guts to a webpage, the page can reach in and steal some organs.

screenshot of error

Ultimately, the error stopped appearing, but the actual fix is unknown to me. The user did clear the browser cache (maybe it was corrupted?) just before it was resolved, but it could also have been a Windows update that resolved the problem, or some other unknown change. At this point, I have no idea how to reproduce it, but hopefully some of the info above will help the next person who runs into it.

like image 78
mwcz Avatar answered Oct 18 '22 14:10

mwcz