Re: [w3c/FileAPI] Stop using the "incumbent settings object" (#60) from Marijn Kruisselbrink on 2017-02-06 (public-webapps-github@w3.org from February 2017)

From: Marijn Kruisselbrink <notifications@github.com>
Date: Mon, 06 Feb 2017 15:29:10 -0800
To: w3c/FileAPI <FileAPI@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/FileAPI/issues/60/277848565@github.com>

Thanks, had a look at the tests. Also played around a bit more with it. Edge seems to indeed (incorrectly) not serialize the origin in the URL. But it's still possibly to tease out what origin it associates with the blob URL by trying to XHR the resulting URL. And with that it seems that only an XMLHttpRequest instance created using the top (web-platform.test:8000) origin is able to read the blob. So at least edge isn't using the current settings object, but other than that the various settings objects always confuse me. Is that actually the incumbent settings object, or is that entry settings object? Either way it still seems reasonable to change the spec to "current" settings object.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/issues/60#issuecomment-277848565

Received on Monday, 6 February 2017 23:29:46 UTC