Many webrtc APIs are out of date

[kaisq]

Describe the Bug

Trying to use a number of newer webrtc APIs does not work. Also, a significant number of the implementation details of various RTC* interfaces have changed.

Steps to Reproduce

Attempt to use any of the newer APIs. For example, one issue has already been documented here: #3394.

Expected Behavior

Using these APIs works.

Actual Behavior

Issues with incorrectly modeled objects when interacting with webrtc in the browser, or compilation errors when expected methods/structs are not available or do not have the correct parameters.

Additional Context

It seems that these many of these files have not been updated since shortly after the spec moved from "Working Draft" to "Candidate Recommendation Draft" in 2018. The spec is now a "Recommendation" and should be significantly more stable.

I have tested out locally copying the entirety of the mozilla webrtc IDLs to replace the existing ones (and add new ones where applicable), and it does generate all the files without any issues using the commands in the "Support More Web APIs" documentation. I am happy to open a PR with these changes if it would be useful.

However, this does contain a significant number of breaking changes. I have seen in a number of previous PRs modifying the webrtc files in this repo that there is significant concern about breaking changes. Also, it looks like there are just a couple items marked "unstable", and I'm not entirely clear what the criteria is for that; both items in question do not seem to be marked unstable in any way in the spec. How would all these things be handled in this case? What's the best way to proceed with getting these updated?

[kaisq]

Here's the diff in question: main...kaisq:wasm-bindgen:update-webrtc-idls

[amacgillivray]

It looks like a lot of the IDLs need updating, not just the webrtc stuff! See #4507