-
Notifications
You must be signed in to change notification settings - Fork 115
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
Redefine SendCodecs and ReceiveCodecs #2935
Conversation
to contain all supported codecs, revealing only those that are "enabled" at any given time. Fixes: #2925
Not sure "editorial" is correct here. It does document the existing browser behavior that implemented but not announced codecs are revealed when they are specifically asked for. But it unblocks the check. |
WG discussion on Feb 20, 2024: Looks like an improvement. |
This issue had an associated resolution in WebRTC February 2024 meeting – 20 February 2024 (Modify the codec description model to ease describing changes #2925 #2935):
|
From @jan-ivar : link definition of "enabled" to a dfn so that what it is is defined in one place. |
Ensure generation of valid markup
Hoisting the @dontcallmedom flag. Can't figure out how to run respec locally to get the error message that listAmendments is complaining about. |
FYI: what was missing was the step of 1 of the amendment markup process - adding the id of the changed section to |
Thank you @dontcallmedom ! (and for reminding me of the documentation link!!) |
are there tests associated with this pull request? I would document them in #2910 (and if not, we should track the need to create them) |
Revert "Merge pull request #2935 from w3c/redefine-codecs"
to contain all supported codecs, revealing only those that are "enabled" at any given time.
Fixes: #2925
Preview | Diff