RTCDataChannelInit maxRetransmits = null causes channel to act as if it were unreliable.
Reported by
useru...@gmail.com,
May 26 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 Steps to reproduce the problem: Create a WebRTC DataChannel with maxRetransmits set to null. Send messages through that channel and make sure there's some amount of UDP packet loss. What is the expected behavior? According to MDN, the default of maxRetransmits is null, and means the datachannel should act as a reliable channel. What went wrong? Some datachannel messages never arrive and are lost, acting as if the channel had maxRetransmits set to 0. Did this work before? N/A Does this work in other browsers? Yes Chrome version: Version 66.0.3359.181 (Official Build) (64-bit) Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 29.0 r0
,
May 28 2018
@Reporter: Please provide sample URL/test case to test this issue from TE end. Any further information on reproducing the issue would help in further triaging of this. Thanks!
,
May 28 2018
I've realized that this can be tested without the need to simulate packet loss by simply reading the maxRetransmit property of the created datachannel. https://jsfiddle.net/srxnsyom/1/ This jsfiddle showcases the problem, null and undefined should behave in the same way.
,
May 28 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 29 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by susan.boorgula@chromium.org
, May 27 2018