This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23989 - Fix broken "Origin of Blob URIs" link to File API spec
Summary: Fix broken "Origin of Blob URIs" link to File API spec
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Media Source Extensions (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: LC
Assignee: Adrian Bateman [MSFT]
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2013-12-03 18:52 UTC by Aaron Colwell
Modified: 2013-12-10 16:44 UTC (History)
3 users (show)

See Also:


Description Aaron Colwell 2013-12-03 18:52:11 UTC
The latest update to the File API removed the "Origin of Blob URIs" section that MSE's "MediaSource Object URL" section was referencing. This means that the MediaSource object no longer has a clear definition for its origin. 

The following is the text that was removed from the File API spec.
"The origin of a Blob URI must be the origin of the script that called URL.createObjectURL. Blob URIs must only be valid within this origin."

We need similar text in the MSE spec or a new reference to a section in the File API spec that clarifies the origin for Blob URIs.
Comment 1 Adrian Bateman [MSFT] 2013-12-10 15:46:51 UTC
The text was removed based on this conversation:
Comment 2 Adrian Bateman [MSFT] 2013-12-10 16:00:10 UTC
I'm not sure we should consider media source object URLs same-origin so I propose that we start conservatively until we can prove that is safe.

To do this I propose that we import the definition we've been using from the old File API draft.

Proposed text: "The origin of the MediaSource object URL is the effective script origin of document that called URL.createObjectURL."

[effective script origin] =
Comment 3 Aaron Colwell 2013-12-10 16:44:36 UTC
Change committed.