RTCPeerConnection does not support setting rtcpMuxPolicy parameter

NEW
Unassigned

Status

()

P3
normal
Rank:
25
2 years ago
a year ago

People

(Reporter: juandebravo, Unassigned)

Tracking

51 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [spec-compliance])

(Reporter)

Description

2 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.37 Safari/537.36

Steps to reproduce:

Create an RTCPeerConnection object configuring the rtcpMuxPolicy value:

// rtcp-mux is optional
new RTCPeerConnection({rtcpMuxPolicy: "negotiate"})

or

// rtcp-mux is mandatory
new RTCPeerConnection({rtcpMuxPolicy: "require"})


Actual results:

RTCP candidates are always gathered, no matter the rtcpMuxPolicy value


Expected results:

When rtcpMuxPolicy is "require", RTCP candidates should not be gathered, as rtcp-mux is mandated.

Based on spec: https://w3c.github.io/webrtc-pc/#rtcrtcpmuxpolicy-enum

Updated

2 years ago
Component: Untriaged → WebRTC: Networking
Product: Firefox → Core
Status: UNCONFIRMED → NEW
backlog: --- → webrtc/webaudio+
Rank: 25
Ever confirmed: true
Priority: -- → P2
Whiteboard: [spec-compliance]
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Depends on: 1402221
You need to log in before you can comment on or make changes to this bug.