W3C home > Mailing lists > Public > public-media-capture@w3.org > August 2013

[Bug 19594] createObjectURL behaviour needs documentation, not BLOB

From: <bugzilla@jessica.w3.org>
Date: Wed, 28 Aug 2013 11:43:06 +0000
To: public-media-capture@w3.org
Message-ID: <bug-19594-5753-UgmQJkoETU@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19594

Harald Alvestrand <harald@alvestrand.no> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|public-media-capture@w3.org |harald@alvestrand.no
            Summary|remove "BLOB" from url      |createObjectURL behaviour
                   |usage for createObjectURL() |needs documentation, not
                   |                            |BLOB

--- Comment #25 from Harald Alvestrand <harald@alvestrand.no> ---
I am changing the subject of this bug to be more appropriate to the discussion.
What we seem to be converging on:

- The behaviour of CreateObjectURL(Mediastream) needs to be documented. In
particular, that it behaves exactly the same as CreateObjectURL(Blob) with
regards to creating references that prevent garbage-collecting the Mediastream.

- The URL that is returned from this CreateObjectURL operation should not start
with the letters "blob:", because it can't be used or dereferenced in the ways
that a "blob:" URL can. This is in line with what implementations do today.

- It would be great if the File API specification had a term we could point to
just say "MediaStream is a FOO", and get the properties we want.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Wednesday, 28 August 2013 11:43:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:19 UTC