Status

()

Core
WebRTC
RESOLVED WONTFIX
5 years ago
5 years ago

People

(Reporter: potch, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
The draft WebRTC spec shows binding a MediaStream to a <video> using its `src` property and URL.createObjectURL(). Ideally, we should be matching this behavior to encourage interop and consistency with other APIs.
I've proposed mozSrcObject for HTML5 on the WHATWG list. I don't think we need to desupport it. In our demos and evangelism we should emphasize createObjectURL.
Sounds like we should consider closing this. Any objections?
Whiteboard: [INVALID?]

Updated

5 years ago
Whiteboard: [INVALID?] → [INVALID?][closeme 3/14/2013]
(Reporter)

Comment 3

5 years ago
(In reply to Robert O'Callahan (:roc) (Mozilla Corporation) from comment #1)
> I've proposed mozSrcObject for HTML5 on the WHATWG list. I don't think we
> need to desupport it. In our demos and evangelism we should emphasize
> createObjectURL.

Does createObjectURL work in Nightly?
(In reply to Potch [:potch] from comment #3)
> (In reply to Robert O'Callahan (:roc) (Mozilla Corporation) from comment #1)
> > I've proposed mozSrcObject for HTML5 on the WHATWG list. I don't think we
> > need to desupport it. In our demos and evangelism we should emphasize
> > createObjectURL.
> 
> Does createObjectURL work in Nightly?

Yes
There are real downsides to createObjectURL, in particular the loss of ever being able to know when the app is done with it (except via OnNavigation or equivalent).
We may want a followon bug to modify examples/demos to be adaptive (or in some cases use createObjectURL(), but I'd prefer adaptive since we generally prefer mozSrcObject
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX

Updated

5 years ago
Whiteboard: [INVALID?][closeme 3/14/2013]
You need to log in before you can comment on or make changes to this bug.