Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What happens when X is omitted from dictionary Y #39

martinthomson opened this issue Mar 20, 2014 · 2 comments

What happens when X is omitted from dictionary Y #39

martinthomson opened this issue Mar 20, 2014 · 2 comments


Copy link

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.

robin-raymond pushed a commit to robin-raymond/ortc that referenced this issue Apr 12, 2014

Support for control of quality, resolution, framerate and layering added, as described in
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
Copy link

aboba commented Apr 12, 2014

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.

On Apr 12, 2014, at 8:07 AM, Robin Raymond <> wrote:

Closed #39#39.

Reply to this email directly or view it on GitHub

Copy link

Yes, let's make specific issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

3 participants