W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2015

Re: What happened to onaddstream?

From: Harald Alvestrand <harald@alvestrand.no>
Date: Tue, 23 Jun 2015 10:55:03 +0200
Message-ID: <55891EE7.30503@alvestrand.no>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
CC: Martin Thomson <martin.thomson@gmail.com>, Peter Thatcher <pthatcher@google.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On 06/22/2015 10:11 PM, Silvia Pfeiffer wrote:
>
>
> On 23 Jun 2015 5:38 am, "Harald Alvestrand" <harald@alvestrand.no 
> <mailto:harald@alvestrand.no>> wrote:
> >
> > On 06/22/2015 06:20 PM, Martin Thomson wrote:
> >>
> >> It's gone from the spec.  Everyone implements it.  It would seem to be
> >> necessary to document it, even if it is only under a "legacy" heading.
> >>
> > It went away when addStream() went away.
> >
> > Instead we have a "track" event that carries an RTCTrackEventInit, 
> containing a receiver, a track and an array of streams (section 5.4).
> >
> > It might be nice to have a separate "stream" event that fires only 
> when a new stream has been created; I don't think it's trivial to shim 
> the "stream" event based on only the information in "track" events.
>
> Widely implemented browser APIs like this shouldn't just disappear 
> from the spec, especially if it's hard to shim it. I'm supportive of 
> getting it back.
>
> Silvia.
>
I've filed https://github.com/w3c/webrtc-pc/issues/245 to track the issue.

The http://w3c.github.io/webrtc-pc/archives/20150202/webrtc.html version 
of the spec was the last time it was specified.

More voices are very welcome!

Harald
Received on Tuesday, 23 June 2015 08:55:35 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:44 UTC