You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the attribute descriptions for RTCDataChannel, there are many verbose sentences that describe the same action as setting the attributes with the default/provided values in RTCDataChannelInit dictionary.
The attribute must be initialized to ... by default and must return the value to which it was set when the RTCDataChannel was created.
Is there any reason why the sections require verbose description of default values? They are not really required since the sections that create data channel initialize the attributes with explicit values already.
6.1 createDataChannel
5. Set channel's ordered, maxPacketLifeTime, maxRetransmits, protocol, negotiated, id and priority attributes to the values of the corresponding members of the dataChannelDict argument, using a value of null if the corresponding dictionary member is missing.
6.2 When an underlying data transport is to be announce
4. Initialize channel's label, ordered, maxPacketLifeTime, maxRetransmits, protocol, negotiated and id attributes to their corresponding values in configuration.
For the attributes with default null value, the sentence can be omitted by making the respective fields in RTCDataChannelInit nullable with default value null.
The text was updated successfully, but these errors were encountered:
Giving maxPacketLifeTime and maxRetransmits default values of null would change the behavior a bit since it implies that the dictionary members need to be nullable. For example:
{ maxPacketLifeTime: null, maxRetrainsmits: 10 }
would be allowed with nullable dictionary members. It currently renders a TypeError. I don't see a problem with making the dictionary members nullable, since the corresponding DataChannel attributes are nullable, but it's not an "editorial" change then.
In the attribute descriptions for RTCDataChannel, there are many verbose sentences that describe the same action as setting the attributes with the default/provided values in RTCDataChannelInit dictionary.
Is there any reason why the sections require verbose description of default values? They are not really required since the sections that create data channel initialize the attributes with explicit values already.
For the attributes with default null value, the sentence can be omitted by making the respective fields in RTCDataChannelInit nullable with default value null.
The text was updated successfully, but these errors were encountered: