This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21082 - remoteDescription and localDescription should return NULL if the PeerConnection has been closed
Summary: remoteDescription and localDescription should return NULL if the PeerConnecti...
Status: RESOLVED WORKSFORME
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 minor
Target Milestone: ---
Assignee: Web RTC Working Group
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-22 09:17 UTC by Per
Modified: 2013-02-26 13:44 UTC (History)
2 users (show)

See Also:

Attachments

Description Per 2013-02-22 09:17:36 UTC 
WebRTC 1.0: Real-time Communication Between Browsers
W3C Editor's Draft 16 January 2013

The spec currently specify that localDescription and remoteDescription return null if they have not been set.
I would also like they returned null if PeerConnection::close has been called.
Comment 1 Adam Bergkvist 2013-02-25 08:22:40 UTC 
From what I've seen, objects in Web APIs usually don't "reset" them selves as they close. I don't think it's necessary to do so unless we're hogging scarce resources.
Comment 2 Per 2013-02-26 13:44:52 UTC 
ok - we will take a more minimalistic approach then and let localDescription, remoteDescription , localStreams and remoteStream return whatever was set before close was called.