W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2014

Re: File API: Blob URL origin

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 1 Jul 2014 08:32:04 +0200
Message-ID: <CADnb78ihCxW8Y+Jd-W_0jx4+5Dem-=7LfVkCqPySD6ZGiBfhpQ@mail.gmail.com>
To: Glenn Maynard <glenn@zewt.org>
Cc: Arun Ranganathan <arun@mozilla.com>, Web Applications Working Group WG <public-webapps@w3.org>
On Tue, Jul 1, 2014 at 1:13 AM, Glenn Maynard <glenn@zewt.org> wrote:
> Why would the identifier not just be the blob URL itself?  The spec
> currently makes the identifier just the scheme data, which seems much more
> complex than it needs to be.  revokeObjectURL should simply be "Remove the
> entry from the Blob URL Store for URL."  If we want to allow revoking URLs
> that have a fragment attached it'd still need to strip it off; Firefox does
> this, but Chrome doesn't.

That works for me. That way we can make this a more generic store if
god forbid we get more of these schemes.


> Also, both Chrome and Firefox treat the entire URL as case-sensitive, eg.
> "Blob:..." won't revoke the URL, or uppercasing the hostname portion in
> Chrome.  Using the whole URL as the identifier makes this easy to do.

Ew, but okay I guess.


> "Subsequent attempts to dereference url must return a network error" should
> be removed.  That should already be the consequence of unregistering the
> URL, so this is a redundant requirement.

Agreed.


-- 
http://annevankesteren.nl/
Received on Tuesday, 1 July 2014 06:32:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:26 UTC