Closed
Bug 862308
Opened 12 years ago
Closed 12 years ago
DataChannel reliable attribute not updated as specified through RTCDataChannelInit object
Categories
(Core :: WebRTC: Networking, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: whimboo, Unassigned)
References
()
Details
(Keywords: testcase)
Attachments
(1 file)
|
263 bytes,
text/html
|
Details |
If you create a DataChannel instance and specify {reliable: false} for the RTCDataChannelInit parameter, so internal attribute is not correctly updated as requested by the spec. It stays at true.
var pc1 = new mozRTCPeerConnection();
var channel = pc1.createDataChannel({reliable: false});
alert("'" + channel.reliable + "' equals 'false'.");
The output here is: 'true' equals 'false'.
| Reporter | ||
Comment 1•12 years ago
|
||
See step 5 at the following location:
http://dev.w3.org/2011/webrtc/editor/webrtc.html#dom-peerconnection-createdatachannel
Comment 2•12 years ago
|
||
This actually changed recently per a recent IETF definition, but the spec isn't up to date.
See http://mozilla.github.io/webrtc-landing/DataChannel_changes.html.
= Invalid.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Comment 3•12 years ago
|
||
I think bug 855623 was the bug that changed this, but Randell can double check this.
Whiteboard: [WebRTC][blocking-webrtc?][spec-compliance]
Updated•12 years ago
|
status-firefox22:
affected → ---
status-firefox23:
affected → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•