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
Attributes in dictionaries are optional. That means that the spec needs to define what happens when an attribute is omitted. For every attribute. The easiest way to do this is to define a default value.
The text was updated successfully, but these errors were encountered:
Support for control of quality, resolution, framerate and layering added, as described inhttps://github.com/w3c/issues/31
RTCRtpListener object added and figure in Section 1 updated, as described in w3c#32
More complete support for RTP and Codec Parameters added, as described in w3c#33
Data Channel transport problem fixed, as described in w3c#34
Various NITs fixed, as described in w3c#37
Section 2.2 and 2.3 issues fixed, as described in w3c#38
Default values of some dictionary attributes added, to partially address the issue described in w3c#39
Support for ICE TCP added, as described in w3c#41
Fixed issue with sequences as attributes, as described in w3c#43
Fix for issues with onlocalcandidate, as described in w3c#44
Initial stab at a Stats API, as requested in w3c#46
Added support for ICE gather policy, as described in w3c#47
Although the Editor's draft makes some progress on this issue, I don't think it is fully addressed yet. There are defaults provided in a number of cases, but the effects of having attributes unset isn't always specified. Maybe the best way to make progress is to close this general issue and open more specific ones.