- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Tue, 23 Jun 2015 20:35:30 +1000
- To: Harald Alvestrand <harald@alvestrand.no>
- Cc: Martin Thomson <martin.thomson@gmail.com>, Peter Thatcher <pthatcher@google.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On Tue, Jun 23, 2015 at 6:55 PM, Harald Alvestrand <harald@alvestrand.no> wrote: > On 06/22/2015 10:11 PM, Silvia Pfeiffer wrote: > > > On 23 Jun 2015 5:38 am, "Harald Alvestrand" <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. The last WD at http://www.w3.org/TR/webrtc/ still has it, too. S.
Received on Tuesday, 23 June 2015 10:36:17 UTC