- From: Arun Ranganathan <arun@mozilla.com>
- Date: Mon, 19 May 2014 15:30:30 -0400
- To: Frederik Braun <fbraun@mozilla.com>
- Cc: glenn Maynard <glenn@zewt.org>, Jonas Sicking <jonas@sicking.cc>, Anne van Kesteren <annevk@annevk.nl>, Boris Zbarsky <bzbarsky@mit.edu>, Web Applications Working Group WG <public-webapps@w3.org>
On May 19, 2014, at 5:33 AM, Frederik Braun <fbraun@mozilla.com> wrote: > On 15.05.2014 22:46, Glenn Maynard wrote: >> On Thu, May 15, 2014 at 12:07 PM, Jonas Sicking <jonas@sicking.cc >> <mailto:jonas@sicking.cc>> wrote: >> >> On Thu, May 15, 2014 at 6:52 AM, Anne van Kesteren <annevk@annevk.nl >> <mailto:annevk@annevk.nl>> wrote: >>> I was thinking about the latter and that would not work if the URL was >>> revoked. Unless we store origin at parse time. >> >> Good point. Without using the explicit syntax we couldn't return a >> consistent result for the origin. >> > > I'm not against the explicit model, but I think it would be very > desirable if there was a way to get the origin out of the blob URL with > some sort of API. > It's not unlikely that developers will implement their own (flawed) URL > parsing to determine the origin of a blob URL, if it's explicitly in the > blob URL. I think this could be done with the existing URL API’s origin attribute so that it does the right thing with a Blob URL: http://url.spec.whatwg.org/#dom-url-origin Of course, right now that won’t work in Fx. I wonder if we could fix that? Or add another static function to URL. —A*
Received on Monday, 19 May 2014 19:31:01 UTC