How to delete a localStorage item when the browser window/tab is closed?
should be done like that and not with delete operator: localStorage.removeItem(key);
should be done like that and not with delete operator: localStorage.removeItem(key);
Quoting from the Wikipedia article on Web Storage: Web storage can be viewed simplistically as an improvement on cookies, providing much greater storage capacity (10 MB per origin in Google Chrome(https://plus.google.com/u/0/+FrancoisBeaufort/posts/S5Q9HqDB8bh), Mozilla Firefox, and Opera; 10 MB per storage area in Internet Explorer) and better programmatic interfaces. And also quoting from a John Resig article … Read more
localStorage and sessionStorage both extend Storage. There is no difference between them except for the intended “non-persistence” of sessionStorage. That is, the data stored in localStorage persists until explicitly deleted. Changes made are saved and available for all current and future visits to the site. For sessionStorage, changes are only available per tab. Changes made … Read more
This is an extremely broad scope question, and a lot of the pros/cons will be contextual to the situation. In all cases, these storage mechanisms will be specific to an individual browser on an individual computer/device. Any requirement to store data on an ongoing basis across sessions will need to involve your application server side … Read more
localStorage only supports strings. Use JSON.stringify() and JSON.parse(). var names = []; names[0] = prompt(“New member name?”); localStorage.setItem(“names”, JSON.stringify(names)); //… var storedNames = JSON.parse(localStorage.getItem(“names”)); You can also use direct access to set/get item: localstorage.names = JSON.stringify(names); var storedNames = JSON.parse(localStorage.names);
Use this to clear localStorage: localStorage.clear();
Cookies and local storage serve different purposes. Cookies are primarily for reading server-side, local storage can only be read by the client-side. So the question is, in your app, who needs this data — the client or the server? If it’s your client (your JavaScript), then by all means switch. You’re wasting bandwidth by sending … Read more
Looking at the Apple, Mozilla and Mozilla again documentation, the functionality seems to be limited to handle only string key/value pairs. A workaround can be to stringify your object before storing it, and later parse it when you retrieve it: var testObject = { ‘one’: 1, ‘two’: 2, ‘three’: 3 }; // Put the object … Read more