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 26017 - CaptureStream should be specified
Summary: CaptureStream should be specified
Status: RESOLVED WONTFIX
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: Media Capture and Streams (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: public-media-capture@w3.org
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-09 07:48 UTC by Harald Alvestrand
Modified: 2014-11-11 15:30 UTC (History)
3 users (show)

See Also:


Attachments

Description Harald Alvestrand 2014-06-09 07:48:28 UTC
From slides presented in Washington DC:

captureStream[UntilEnded]
❖ For a media element (<video>, <audio>), be able to 
create a media stream from its contents!
❖ Great for web audio!
❖ … also a potential source of WebRTC streams!
❖ captureStream generates media from the source!
❖ captureStreamUntilEnded stops when the stream ends!
❖ Switching sources causes this to end
Comment 1 Harald Alvestrand 2014-10-09 09:40:11 UTC
This seems to have been filed under the wrong component.
Comment 2 Harald Alvestrand 2014-10-09 14:14:42 UTC
This is not a blocker on the Media Capture spec. The proper place to do this is in the HTML5 specification.
Comment 3 Stefan Hakansson LK 2014-11-11 14:38:18 UTC
Already in Washington DC (I think) we concluded this would be a separate document. There is now a repo created in github: https://github.com/w3c/mediacapture-fromelement (still empty) and the initial Editor's appointed are Martin Thomson and Shijun Sun.

I now close this bug as "wontfix" as a) a fix is underway and b) it does not read on the "Media Capture and Streams" document.
Comment 4 Jan-Ivar Bruaroey [:jib] 2014-11-11 15:30:59 UTC
Hmm, where should issues for that go then?

Rather than closing it, isn't there another component we can use?