News for hackers. Stuff that matters.
Re:We need to kill off the localStorage API by newman314 on Tuesday February 28, 2012 @06:32AM (#3642793)
I would like to see more tools to see what is stored inside localStorage. Right now, afaik, there is not easy way to inspect.
Re:We need to kill off the localStorage API by mike-cardwell on Tuesday February 28, 2012 @08:48AM (#3643104)

  for( var i = localStorage.length - 1; i >= 0; --i ){
     var key = localStorage.key(i);
     console.log( key + ": " + localStorage.getItem(key) );
  }
Re:We need to kill off the localStorage API by pixelcort on Tuesday February 28, 2012 @01:18PM (#3644178)
Tip: To get a random localStorage key:

    localStorage.key(Math.random()*localStorage.length)
Re:We need to kill off the localStorage API by wslh on Tuesday February 28, 2012 @06:54AM (#3642851)
It is a sqlite database (in Google Chrome and Firefox), so with the sqlite console you can access the database.
Re:We need to kill off the localStorage API by kinlan on Tuesday February 28, 2012 @06:34AM (#3642799)
Chrome DevTools and Safari (and I am sure FF) have had tools for a long time to see inside localStorage. It is inspection tools for IndexedDB we haven't got.
Re:We need to kill off the localStorage API by kinlan on Tuesday February 28, 2012 @06:42AM (#3642823)
Actually according to http://peter.sh/2012/02/scoped-styles-deflated-websockets-an... we now have IndexedDB inspection in the latest Chromium (behind a flag).
Re:We need to kill off the localStorage API by masklinn on Tuesday February 28, 2012 @06:53AM (#3642848)
> and I am sure FF

It's pretty primitive, you have to go into the DOM tab for `window` and scroll down to `localStorage`.

Same for `globalStorage`.