[Webkit-unassigned] [Bug 174314] New: RTCPeerConnection's close method should update signalingState
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Jul 10 10:37:50 PDT 2017
https://bugs.webkit.org/show_bug.cgi?id=174314
Bug ID: 174314
Summary: RTCPeerConnection's close method should update
signalingState
Product: WebKit
Version: Safari Technology Preview
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: WebCore JavaScript
Assignee: webkit-unassigned at lists.webkit.org
Reporter: mroberts at twilio.com
Run the following code:
(async () => {
console.log('1. Constructing an RTCPeerConnection')
const pc = new RTCPeerConnection()
const signalingStateChangeEvent = new Promise(resolve => pc.onsignalingstatechange = resolve)
console.log('2. Closing the RTCPeerConnection')
pc.close()
if (pc.signalingState !== 'closed') {
console.error(`Expected the RTCPeerConnection's signaling state to be "closed", not "${pc.signalingState}"`)
}
console.log('3. Awaiting a "signalingstatechange" event')
await signalingStateChangeEvent
console.log('Success!')
})()
Expected output (Chrome, Firefox):
1. Constructing an RTCPeerConnection
2. Closing the RTCPeerConnection
3. Awaiting a "signalingstatechange" event
Success!
Actual output (Safari):
1. Constructing an RTCPeerConnection
2. Closing the RTCPeerConnection
Expected the RTCPeerConnection's signaling state to be "closed", not "stable"
3. Awaiting a "signalingstatechange" event
In the actual output, "Success!" never prints because `signalingStateChangeEvent` never resolves. I guess the behavior around this was only recently specified here?
https://github.com/w3c/webrtc-pc/pull/1371
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170710/7d2eb8fe/attachment.html>
More information about the webkit-unassigned
mailing list