[Bug 25914] No definition of parsing blob's scheme data

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25914

--- Comment #23 from Arun <arun@mozilla.com> ---
(In reply to Glenn Maynard from comment #22)
> (In reply to Anne from comment #21)
> > Again, the whole origin check is largely unneeded as I explained due to the
> > blob URL store being scoped to browsing contexts that can reach each other
> > which is document.domain reach. For browsing contexts with unique origins
> > that's obviously only same-origin browsing contexts and therefore the whole
> > null thing is kind of irrelevant.
> 
> I don't remember any discussion about "the whole origin check is largely
> unneeded", but that's the same as what I said: doing the origin check
> through the blob URL store (implicit) and not by comparing something
> serialized into the URL (explicit).


Well, let's discuss the origin check and properly defining the Blob URL Store
in the bug Anne filed for it, namely Bug 25987 .

Anne: in order to get *this* bug right, tell me if this is the right approach:

1. Use Basic URL Parser to parse a Blob URL into relevant components. File API
is chiefly interested in scheme data, though presently we allow fragment but
make no explicit mention of any other URL components.

2. Since the scheme data portion returned by 1. above is itself a URL, run the
Basic URL Parser again on the scheme data component returned by 1. Since scheme
data is itself a Unicode serialized origin string, the scheme, host, port tuple
should suffice for origin extraction without string manipulation heroics that
the spec now has. Strictly speaking, if we get Bug 25987 right, this may not be
necessary, but good to have around.

OK?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 9 June 2014 17:37:57 UTC