New issue
Advanced search Search tips

Issue 823144 link

Starred by 2 users

Issue metadata

Status: Fixed
Closed: Dec 12
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug

Show other hotlists

Hotlists containing this issue:

Sign in to add a comment

implement RTCPeerConnection.connectionState

Reported by, Mar 18 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/64.0.3282.167 Chrome/64.0.3282.167 Safari/537.36

Steps to reproduce the problem:
1. check 'connectionState' in RTCPeerConnection

What is the expected behavior?
see et al

What went wrong?
Chrome mixes up connectionstate and emits a combined ice/dtls state as iceconnectionstatechange.

Migrating developers might actually be the bigger problem here. Adding connectionState as an alias for iceConnectionState might be a good first step.

Also this makes it look like chrome has a significantly higher iceconnection setup time (30%) than Firefox since in Chrome the setup time includes the DTLS handshake whereas in Firefox it does not.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 64.0.3282.167  Channel: n/a
OS Version: 
Flash Version:
Labels: Needs-Triage-M64

Comment 2 by, Mar 19 2018

Components: -Blink>WebRTC Blink>WebRTC>PeerConnection
Status: Assigned (was: Unconfirmed)
Status: Started (was: Assigned)
Project Member

Comment 4 by, Nov 23

The following revision refers to this bug:

commit 93094c4962f94a897a6601a75724e4b2db329fae
Author: Jonas Olsson <>
Date: Fri Nov 23 14:42:26 2018

Add RTCPeerConnection.connectionState and onconnectionstatechange.

Intent to Implement and Ship:

Bug:  chromium:823144 
Change-Id: Ia849f44d1c8898da0fcb8341c8ff56de4de2d815
Commit-Queue: Jonas Olsson <>
Reviewed-by: Philip Jägenstedt <>
Reviewed-by: Guido Urdaneta <>
Reviewed-by: Henrik Boström <>
Cr-Commit-Position: refs/heads/master@{#610603}

Status: Fixed (was: Started)

Sign in to add a comment