RTCRtpReceiver.getParameters() and friends - return value not dict#24503
RTCRtpReceiver.getParameters() and friends - return value not dict#24503hamishwillee merged 10 commits intomainfrom
Conversation
Preview URLs (8 pages)
Flaws (15)Note! 1 document with no flaws that don't need to be listed. 🎉 URL:
URL:
URL:
URL:
URL:
URL:
URL:
(comment last updated: 2023-02-24 03:10:35) |
| - `rtcp` | ||
| - : An {{domxref("RTCRtcpParameters")}} object providing the configuration parameters used for {{Glossary("RTCP")}} on the sender or receiver. | ||
| This parameter cannot be changed once initially set. | ||
| - `degradationPreference` {{deprecated_inline}} {{optional_inline}} <!-- removed from spec. May have been or be in chrome --> |
There was a problem hiding this comment.
FYI, I made the objects from the get call match the objects in the set call. This degradationPreference was revoked from spec and is not in BCD, but may be in some versions of chrome.
There was a priority field I removed because it never had an impl..
| "asadotzler" | ||
| ] | ||
| }, | ||
| "Web/API/Document_object_model/Using_the_Document_Object_Model": { |
There was a problem hiding this comment.
Side comment, I wonder why this is in this PR...
There was a problem hiding this comment.
Ok, it is lexicographic ordering fix. I will investigate this in a separate PR. This is harmless.
|
Still a small redirect problem (orphaned pages) to fix and this is good to go. |
|
This pull request has merge conflicts that must be resolved before it can be merged. |
1 similar comment
|
This pull request has merge conflicts that must be resolved before it can be merged. |
8c8375e to
b2ebec8
Compare
|
@teoli2003 Thanks for the review. I have rebased. Can I ignore the build error about redirects ... and if not, how to I fix this? I did the redirects in the "normal" way using the redirect option when deleting. |
f4ad41a to
fd8aa86
Compare
fd8aa86 to
91bb4d5
Compare
|
@teoli2003 The redirects from this are definitely correct - i.e. the message says the files don't exist, but they most definitely do. Further I used the proper tools to create these redirects so I'm not sure what else I can do. I think it might be a lint issue. OK to merge this and see if it breaks anything? |
|
It looks like there's an issue with this one: yarn content fix-redirects en-us
removing orphaned redirect (from exists): /en-US/docs/Web/API/RTCRtpParameters /en-US/docs/Web/API/RTCRtpSender/setParameters
info: Fixed en-us
yarn content validate-redirects en-us --strict
info: ✓ redirects for en-us looking good!
info: 🍾 All is well in the world of redirects 🥂 |
|
Shall we remove this line in the redirect (using |
|
The problem is we're adding a redirect from a page that exists: |
|
@bsmth That shouldn't be the problem because this PR deletes that file. Though as you say, that is what is reported. I'm going to remove the redirects from this PR, merge, and recreate them in another. |
This continues the work started in #24239 of removing the dictionaries RTCRtpParameter, RTCRtpReceiveParameters, RTCRtpSendParameters in
RTCRtpReceiver.setParameters(),RTCRtpReceiver.getParameters(),RTCRtpReceiver.setParameters()replacing them with objects.The associated work for BCD has already been done in mdn/browser-compat-data#18834
This is part of the work for #23677