-
@lorenschmidt I will say that I'm surprised this works!
-
@lorenschmidt sorry, that wasn't very helpful - I assumed this wouldn't work because the same domain policy for file:// urls generally assumes that all paths should be treated as if they have a different origin
-
@lorenschmidt some stuff is exempt from those rules, for historical reasons - image files (tho you can't inspect the pixels, just display them) and JS files. but it's a narrow window to fit through.
-
@lorenschmidt but... if it works, it works. generally, tho, the problem with this kind of stuff is not whether you're creating a security hole, but whether you can get around the security rules.
-
@lorenschmidt (this is why my designed-to-work-on-localhost system loads all of it's data from a js import that just contains "var data = [big blob of json]" rather than loading an actual .json file)