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 25859 - Streams that become isolated generate errors on PC
Summary: Streams that become isolated generate errors on PC
Status: RESOLVED LATER
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Martin Thomson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-21 19:34 UTC by Martin Thomson
Modified: 2014-12-15 10:39 UTC (History)
3 users (show)

See Also:

Attachments

Description Martin Thomson 2014-05-21 19:34:53 UTC 
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.
Comment 1 Harald Alvestrand 2014-10-31 17:57:06 UTC 
Martin will make PR.
Comment 2 Harald Alvestrand 2014-10-31 18:01:22 UTC 
This needs some more thinking; not PR-ready.
Comment 3 Adam Bergkvist 2014-11-05 10:20:21 UTC 
This event can use the MediaStreamTrackEvent interface [1].

[1] http://w3c.github.io/mediacapture-main/#mediastreamtrackevent
Comment 4 Martin Thomson 2014-11-05 17:11:59 UTC 
(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.
Comment 5 Adam Bergkvist 2014-11-10 13:38:14 UTC 
Even better. We can use a simple Event.
Comment 6 Dominique Hazael-Massieux 2014-12-15 10:39:19 UTC 
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.