Issue metadata
Sign in to add a comment
|
PeerConnectionTracker to track new RTP Media API calls for chrome://webrtc-internals |
||||||||||||||||||||||
Issue descriptionThe legacy APIs for handling media, addStream/removeStream/getLocalStreams/getRemoteStreams, are tracked by PeerConnectionTracker. But the spec-compliant addTrack/removeTrack/getSenders (first release in M64, with more features to be implemented) and getReceivers are not logged by PeerConnectionTracker. Since we should begin to use the new RTP Media APIs and deprecate the old, chrome://webrtc-internals should track these calls.
,
Jul 31
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by hbos@chromium.org
, Feb 8 2018