W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2014

[Bug 25859] New: Streams that become isolated generate errors on PC

From: <bugzilla@jessica.w3.org>
Date: Wed, 21 May 2014 19:34:53 +0000
To: public-webrtc@w3.org
Message-ID: <bug-25859-4991@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25859

            Bug ID: 25859
           Summary: Streams that become isolated generate errors on PC
           Product: WebRTC Working Group
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebRTC API
          Assignee: public-webrtc@w3.org
          Reporter: martin.thomson@gmail.com
                CC: public-webrtc@w3.org

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Wednesday, 21 May 2014 19:34:54 UTC

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