Bug 124856 - URL.createObjctURL() should work for MediaStream objects
Summary: URL.createObjctURL() should work for MediaStream objects
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Roger Zanoni
URL:
Keywords:
Depends on:
Blocks: 121943
  Show dependency tree / graph
 
Reported: 2013-11-25 13:29 PST by Nick Diego Yamane (diegoyam)
Modified: 2013-11-25 15:20 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Diego Yamane (diegoyam) 2013-11-25 13:29:31 PST 
When the createObjectURL() method is called with a MediaStream argument, the user agent must return a unique Blob URL for the given MediaStream.
For audio and video streams, the data exposed on that stream must be in a format supported by the user agent for use in audio and video elements.

http://www.w3.org/TR/mediacapture-streams/#url
Comment 1 Eric Carlson 2013-11-25 14:43:41 PST 
createObjectURL has been removed from the latest editor's draft: http://dev.w3.org/2011/webrtc/editor/getusermedia.html#change-log
Comment 2 Nick Diego Yamane (diegoyam) 2013-11-25 15:20:17 PST 
Looks like URL.createObject() will be replaced by "direct assigment" mechanism.

http://www.w3.org/TR/mediacapture-streams/#direct-assignment-to-media-elements