CKTIS / JavaScript
Shramba brskalnika
Shramba brskalnika vključuje mehanizme okolja brskalnika za shranjevanje podatkov na strani odjemalca. Spoznajte razliko med localStorage in sessionStorage ter mejo med jezikom ECMAScript in spletnimi API-ji.
Različica: ECMAScript and Web APIs; exact feature edition and browser support reviewed per entry; Node 24 in repository does not prove browser API support
Sintaksa
localStorage.setItem(key, value);
localStorage.getItem(key);
localStorage.removeItem(key);Shramba brskalnika (browser storage) je funkcija okolja, ne sintaksa ECMAScripta. Specifikacija ECMAScripta opisuje jezik in njegovo interakcijo z gostiteljskim okoljem; ne določa localStorage ali sessionStorage. Prisotnost Node 24 v repozitoriju ne dokazuje, da sta ta vmesnika na voljo v ciljnem brskalniku.
localStorage ohranja pare ključ-vrednost med sejami, medtem ko je sessionStorage vezan na sejo strani v določenem zavihku. Oba vmesnika sta sinhrona in shranjujeta nize. Če ključ ne obstaja, getItem(key) vrne null. Objekte lahko shranite z JSON.stringify in preberete z JSON.parse.
Dostop je odvisen od izvora strani in pravil brskalnika. Podatki se lahko odstranijo, dostop ali zapis pa lahko sproži izjemo. Te shrambe ne obravnavajte kot edine kopije podatkov ali kot prostora za skrivnosti. Razdelek Web Storage standarda HTML skupine WHATWG opredeljuje localStorage in sessionStorage ter njune metode. Ni vir podatkov o združljivosti z brskalniki in ne zagotavlja, da sta ta vmesnika na voljo v ciljnem brskalniku.
Primeri
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Browser storage example</title>
</head>
<body>
<p>localStorage can persist across visits. sessionStorage is scoped to the page session in a tab. Both are browser APIs, not part of ECMAScript.</p>
<ul aria-label="Storage check results">
<li id="localStorage"></li>
<li id="sessionStorage"></li>
</ul>
<script>
const fixture = JSON.stringify({ theme: 'dark' });
function checkStorage(name) {
const result = document.getElementById(name);
try {
const store = window[name];
// A fresh temporary key avoids reusing application keys. This sequence is not atomic:
// another same-origin tab can change localStorage between calls.
const key = `cktis:storage:example:${crypto.getRandomValues(new Uint32Array(4)).join('-')}`;
if (store.getItem(key) !== null) {
throw new Error('Temporary storage key already exists');
}
store.setItem(key, fixture);
let saved;
try {
saved = store.getItem(key);
} finally {
store.removeItem(key);
}
if (saved !== fixture || store.getItem(key) !== null) {
throw new Error('Round trip or cleanup failed');
}
result.textContent = `${name}: read back theme=${JSON.parse(saved).theme}; temporary key removed.`;
} catch (error) {
if (!(error instanceof DOMException) || !['SecurityError', 'QuotaExceededError'].includes(error.name)) {
throw error;
}
result.textContent = `${name}: temporary write unavailable (${error.name}).`;
}
console.log(result.textContent);
}
checkStorage('localStorage');
checkStorage('sessionStorage');
</script>
</body>
</html>Rezultat
A successful check reports that it read back theme=dark and removed the temporary key. If the check catches a DOMException named SecurityError or QuotaExceededError, it reports that the temporary write is unavailable and includes the error name. Other errors, including a temporary-key collision or a detected round-trip or cleanup failure, are rethrown without a report for that storage area. If the localStorage check rethrows, the sessionStorage check does not run.
Prikazana koda in navedeni rezultat sta bila preverjena v izoliranem okolju z metodo, zapisano v dokazilu o preverjanju te natančne različice.