Closed Bug 855304 Opened 11 years ago Closed 11 years ago

RTCPeerConnection must support signalingState attribute

Categories

(Core :: WebRTC: Signaling, defect)

Product:
Core
Component:
WebRTC: Signaling
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 857894

People

(Reporter: snandaku, Unassigned)

Details

(Whiteboard: [WebRTC][blocking-webrtc-][spec-issue]) 

W3C WebRTC spec defines signalingState as readonly attribute on RTCPeerConnection interface here: http://dev.w3.org/2011/webrtc/editor/webrtc.html#interface-definition
Per today's triage, we aren't going to block on any attribute analysis style bugs anymore.
Whiteboard: [WebRTC][blocking-webrtc-][spec-issue]
Turns out all we have to do here is rename the readyState attribute to signalingState to fix this after seeing Chrome Canary's implementation. I'll move this over to the new bug that makes this clear.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.