25859 2014-05-21 19:34:53 +0000 Streams that become isolated generate errors on PC 2014-12-15 10:39:19 +0000 1 1 1 Unclassified WebRTC Working Group WebRTC API unspecified PC All RESOLVED LATER P2 normal --- 1 martin.thomson martin.thomson adam.bergkvist harald public-webrtc oldest_to_newest 106604 0 martin.thomson 2014-05-21 19:34:53 +0000 When a stream becomes isolated (see 25856) we should surface an error and stop sending media for that track (we might have to continue transmission - ask the IETF group - but no content can be sent). The only exception to this is if the stream is isolated and peerIdentity tagged. Those can potentially be transmitted. Proposal is: partial interface RTCPeerConnection : EventTarget { attribute EventHandler? onerror; }; [Constructor(TrackIsolatedEventInit args)] interface TrackIsolatedEvent : Event { attribute MediaStreamTrack track; }; Alternatively: partial interface RTCRtpSender : EventTarget { attribute EventHandler? onerror; }; Which might be a little better because the error can be generic. 114376 1 harald 2014-10-31 17:57:06 +0000 Martin will make PR. 114378 2 harald 2014-10-31 18:01:22 +0000 This needs some more thinking; not PR-ready. 114547 3 adam.bergkvist 2014-11-05 10:20:21 +0000 This event can use the MediaStreamTrackEvent interface [1]. [1] http://w3c.github.io/mediacapture-main/#mediastreamtrackevent 114564 4 martin.thomson 2014-11-05 17:11:59 +0000 (In reply to Adam Bergkvist from comment #3) > This event can use the MediaStreamTrackEvent interface [1]. It doesn't need to. event.target will identify the track since the event is fired at the track. 114745 5 adam.bergkvist 2014-11-10 13:38:14 +0000 Even better. We can use a simple Event. 116305 6 dom 2014-12-15 10:39:19 +0000 WebRTC API bugs have been moved to github issues: https://github.com/w3c/webrtc-pc/issues Please subscribe to the issues you want to keep watching.