Open Bug 1265827 Opened 6 years ago Updated 3 days ago

Add support for RTCPeerConnectionState in RTCPeerConnection

Categories

(Core :: WebRTC, defect, P2)

45 Branch
defect

Tracking

()

People

(Reporter: rajmohanbanavi, Unassigned, NeedInfo)

References

(Blocks 2 open bugs)

Details

(Keywords: dev-doc-needed)

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.75 Safari/537.36

Steps to reproduce:

The current WebRTC spec mentions about RTCPeerConnectionState read only attribute in the peer connection object.


Actual results:

Did not locate this attribute in the pc object


Expected results:

Need to add support for the same.
Rank: 29
Priority: -- → P2
The RTCPeerConnectionState enum has been documented: https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection#RTCPeerConnectionState_enum

RTCPeerConnection.connectionState has also been documented: https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/connectionState

The compatibility table on connectionState indicates the lack of implementation.

Leaving this in doc-needed state, however, because additions will have to be made to Firefox X for developers once it's implemented.
There has been no update to this bug in a few months.
Can this be prioritized please?
Thanks!
Any update on this?
Blocks: webrtc_spec
Rank: 29 → 19
Priority: P2 → P1
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Chrome just landed connectionState in Chrome 72.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Since the PeerConnectionState appears to be an aggregate of ICE connection state and DTLS connection state I'm not sure if it makes sense to try to implement this without implementing the DTLS connection object as well.

This is already causing timeouts in at least some web-platform-tests from upstream.

Blocks: 1533020
Priority: P3 → P2

Hello!
Coming back to this in 2021, I wonder if there is a particular reason why this API is sitting at P2 (for years!) and not getting implemented?

Related:

I was also iterating through some links over MDN docs & GitHub side, someone suggested using RTCPeerConnection.iceConnectionState as a workaround but according to the standard (and also MDN covers this very well), that wouldn't cover the exact same connection state information & behavior.

So, I wanted to bump this thread up to get more information.
Hopefully, this ticket would be triaged to higher priority so that an implementation might get into the next FF release cycle :)

Subscribes to dtls changes and aggragates them together with the iceConnectionState.
The aggregates state is exposed as RTCPeerConnection.connectionState.
The respective events are dispatched for connectionstatechange

Assignee: nobody → rudi.floren
Status: NEW → ASSIGNED
Attachment #9256529 - Attachment description: WIP: Bug 1265827 - Add connectionState to RTCPeerConnection. r?ng → Bug 1265827 - Add connectionState to RTCPeerConnection. r?ng
Attachment #9256529 - Attachment description: Bug 1265827 - Add connectionState to RTCPeerConnection. r?ng → Bug 1265827 - Add connectionState to RTCPeerConnection. r=jib

Sorry for taking so long with this. Will try to get to review tomorrow.

The bug assignee didn't login in Bugzilla in the last months and this bug has priority 'P2'.
:mjf, could you have a look please?
For more information, please visit auto_nag documentation.

Assignee: rudi.floren → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(mfroman)

(In reply to Jan-Ivar Bruaroey [:jib] (needinfo? me) from comment #13)

Sorry for taking so long with this. Will try to get to review tomorrow.

:jib - have you had a chance to look at the patch?

Flags: needinfo?(mfroman) → needinfo?(jib)
You need to log in before you can comment on or make changes to this bug.