local-storage

问题 I have some general questions which are bothering me regarding the context API and local storage. When to use local storage?, when to use the Context API and when would I use both? I know that to persist data after the refresh I need something like local storage or session storage, so do I ditch the context API entirely and just store everything in the local storage? this way I can not only store data but also keep it on refresh? some insight would be really helpful. What are some pros and

问题 I have a user interface that interacts with some software. My user interface displays a database with data paths. The user selects the data paths they want to simulate/run, and that sends the data path to the software. After its finished the output is an excel report saved in a folder on the same computer. This is were I'm a bit stuck on how exactly I'm supposed to show the excel report to the user for the specified data path the user selected to simulate/run. My idea was to create a routine

问题 This discussion is the spin off of this post:passing-variables-between-pages, I have edited the question in order to provide More clarity on the scripts, please who will give any answers to use denomination used in this version. A.html <form action="b.html"> // username field, let's say "Macbeth" <input type="text" id="txt"/> <input type="submit" value="nome" onClick="passvalues();"/> </form> <span id="result">Macbeth</span> // display username <script> function passvalues() { var nme =

问题 This discussion is the spin off of this post:passing-variables-between-pages, I have edited the question in order to provide More clarity on the scripts, please who will give any answers to use denomination used in this version. A.html <form action="b.html"> // username field, let's say "Macbeth" <input type="text" id="txt"/> <input type="submit" value="nome" onClick="passvalues();"/> </form> <span id="result">Macbeth</span> // display username <script> function passvalues() { var nme =

问题 I have a form in which I ask users for their input. I will then store the input in the local storage. let shape = { shape: shape, color: shapeColor, dimension: noOfDimension, } arr.push(shape) window.localStorage.setItem("arr", JSON.stringify(arr)) Now I have a button in which when I click on it, a modal pops up and display the shapes stored. The shape data can be retrieved by JSON.parse(localStorage.getItem("arr")) . However the problem is, when I were to add new shape data again, it will

问题 I have a form in which I ask users for their input. I will then store the input in the local storage. let shape = { shape: shape, color: shapeColor, dimension: noOfDimension, } arr.push(shape) window.localStorage.setItem("arr", JSON.stringify(arr)) Now I have a button in which when I click on it, a modal pops up and display the shapes stored. The shape data can be retrieved by JSON.parse(localStorage.getItem("arr")) . However the problem is, when I were to add new shape data again, it will

问题 I'm trying to make a localStorage object reactive, so that if it updates, it will also update in other tabs using that same object. I'm using Vue.js and have tried to create a computed property that returns the localStorage object, but this doesn't work. How can I make the object reactive and make it update in other browser tabs also? computed: { localStorageObject() { return JSON.parse(localStorage.getItem('object')); } } 回答1: @Matthias has the start of an answer, but it won't react to

问题 If I have a page A, and it loads several iframes B,C,D,E,F. And in each iframe, there is javascript code that stores a key color with value red in local storage. Will all the iframes local storage collide or is each one independent? If it is not independent, is there a way to make it independent? Thanks 回答1: According to the W3C: Local storage is per origin (per domain and protocol). All pages, from one origin, can store and access the same data. In other words, if the iframes all reside in

问题 Question: How do I create a workaround to save state between incognito windows on Mozilla? Description: I have an application which is dependent on localStorage. I went into a weird situation where when a user is using the application in incognito mode. And when he duplicate the window in Mozilla incognito mode(second window). The properties in localStorage are missing. When he duplicates the window again(third window), we are able to access localStorage properties. This is only happening in

问题 After doing a bit of research on this topic, it seems like session keys have typically been stored as cookies which is nice because they get automatically added to requests. I've been seeing that developers prefer localstorage to cookies due to less restrictions, though. I am building a React frontend, so persisting a reducer in localstorage and managing the session key in that reducer would be very easy. I would need to append this to requests, which seems to be the only downside. Wondering