commit | 44e5d5a9d1bdd78310d1e599c70d87651928e1e7 | [log] [tgz] |
---|---|---|
author | Evan Shrubsole <eshr@webrtc.org> | Wed Jan 18 10:28:12 2023 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 18 10:34:03 2023 |
tree | 5a6bcb9391f95f1eb8c6ffc36946467ef1db194b | |
parent | 2c0376e20ceef4459295f873c18ff2f417f17bb1 [diff] |
Revert "Ensure RTCRtpSenders are always created with one encoding" This reverts commit b8023690d9f0e150cfe698cd68b477903ac66178. Reason for revert: Breaking WPT tests in Chrome. Example build https://ci.chromium.org/ui/p/chromium/builders/try/linux-rel/1263191/overview Original change's description: > Ensure RTCRtpSenders are always created with one encoding > > It is possible to have AddTransceiver calls with an empty array > of encodings or AddTrack calls. In both cases, before negotiation, > the sender's encodings array would be empty and it was not possible > to update any value. > > Now, a default entry should be created in those cases, allowing to > update the configuration before negotiation. > > Bug: webrtc:10567 > Change-Id: I1271e2965e1a97c1e472451e0ab8867fc24f6c2b > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/290994 > Auto-Submit: Florent Castelli <orphis@webrtc.org> > Reviewed-by: Henrik Boström <hbos@webrtc.org> > Commit-Queue: Florent Castelli <orphis@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#39126} Bug: webrtc:10567 Change-Id: Ib8931b38182251baac616540788a02a5fafaf670 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/291120 Bot-Commit: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Evan Shrubsole <eshr@webrtc.org> Auto-Submit: Evan Shrubsole <eshr@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/main@{#39132}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.