I work as a technical writer for a software company where we package and ship HTML help files along with our software. Our help needs to be responsive when it's installed and opened in a local file system, and we've been unable to get sessionStorage (or localStorage) to pass variables to another page unless they're in the same Windows directory. This makes the browser's storage unreliable, as the variables we need are different depending on what directory you're in. I understand that to protect against attack pages traversing, say, your Downloads folder, there are various restrictions on file:// access. But is this meant to affect DOM storage as well?