Re: [w3c/FileAPI] Fix several issues with the "Serialization of a Blob URL" algorithm. (#61) from Marijn Kruisselbrink on 2017-01-31 (public-webapps-github@w3.org from January 2017)

From: Marijn Kruisselbrink <notifications@github.com>
Date: Tue, 31 Jan 2017 11:31:30 -0800
To: w3c/FileAPI <FileAPI@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/FileAPI/pull/61/c276466552@github.com>

> I suspect implementations do not actually use incumbent here, so I'll sign up to write tests and submit a follow up PR if the tests bear out my suspicions. For now leaving it as incumbent seems fine.

Awesome. Yeah, I have no idea if browsers are currently using incumbent or not, but it's what the spec was already saying (https://w3c.github.io/FileAPI/#originOfBlobURL), so I just kept that for now.

-- 
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/pull/61#issuecomment-276466552

Received on Tuesday, 31 January 2017 19:32:08 UTC