825562 - Creating a PeerConnection object and checking the ice connection state - should be initialized to an acceptable starting ice connection state, but instead is "undefined"

Status: NEW

(Core :: WebRTC: Networking, defect, P3)

Description

[Jason Smith [:jsmith]]

Steps:

1. Load the attached test case
2. Create a peer connection object
3. View the peer connection attributes

Expected:

The ice state should be initialized - not entirely 100% sure which one as the spec contradicts itself (http://dev.w3.org/2011/webrtc/editor/webrtc.html#idl-def-RTCIceState) in two points. Someone will have to clarify what's the right starting value.

Actual:

The ice state is undefined.

Comment 1

[Jason Smith [:jsmith]]

Attachment: Test Case

Comment 2

[Jason Smith [:jsmith]]

Note - this should be titled - "iceConnectionState"

Comment 4

[Eric Rescorla (:ekr)]

Byron, is this still relevant?

Comment 5

[Byron Campen [:bwc]]

I'll look into it once I'm back.

Comment 6

[Byron Campen [:bwc]]

Ok, this seems to be handled in PeerConnection.js. The getter for the ice connection state does not pull the data from c++, it is cached in js based on state change callbacks, and is indeed not given an initial value.

Comment 7

[Bulk Bug Changes for mreavy's org]

Mass change P2->P3 to align with new Mozilla triage process.

Comment 8

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee is inactive on Bugzilla, so the assignee is being reset.

Comment 9

[Suhaib Mujahid [:suhaib]]

Sorry, there was a problem with the detection of inactive users. I'm reverting the change.

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee is inactive on Bugzilla, so the assignee is being reset.