Discussion on "Client-Side Storage in JavaScript"

Victoria Lo · 2020-07-12T11:33:31.840Z

Hello and welcome to the 2nd article of the #2Articles1Week challenge series! I'm very excited to partake in this challenge. If you haven't heard about the #2Articles1Week challenge, learn more about it here. Firstly, thank you to everyone who read ...

Thank you for this post, Victoria

You said something about localStorage being accessible anywhere on the browser.

Can you give more insights on this?

Sure! I can illustrate this using the Inspector Window. If you are unsure of what it is: visit here.

For localStorage, you can access and view it on the Inspector Window. It will be there, 1 localStorage shared across all your tabs. Data persists even after the browser closes and opens again.

For sessionStorage, you can view it on the Inspector too however, you will notice each page will have its own sessionStorage and its data would disappear if the page/browser is closed.

Victoria Lo I think I get it now.

You mean for the same web address, the localstorage is shared across multiple tabs

I previously thought you meant the data in localstorage from one web address can be accessed by another

Osinachi Chukwujama Yes it's per domain and port (like same origin policy).

This was worth my time, gave it a share also. Thank you for sharing :)

Thank you. Great article. I love the "CRUD Examples" format. I hope you don't mind if I borrow that some of my posts.

No problem! Feel free to use it!

Thank you. Your article is very helpful.

I noticed this issue:

let openRequest = indexedDB.open('database', 1);
// users is the database name and 1 is the version

There is no "users" in your code.

Thanks for pointing that out! I have corrected it :)

Discussion

Client-Side Storage in JavaScript

Responses(4)

Recent in Forum

Search Hashnode

Client-Side Storage in JavaScript

Responses(4)

Recent in Forum