186188 2018-06-01 01:27:33 -0700 Need to implement WebRTC "Unified Plan" for multiple streams 2018-06-06 01:42:55 -0700 1 1 1 Unclassified WebKit WebRTC Safari 11 All All NEW P2 Major --- 1 cwehrung webkit-unassigned fippo lee youennf oldest_to_newest 1429170 0 cwehrung 2018-06-01 01:27:33 -0700 Firefox only supports unified plan and Chrome has now aggressively started moving towards it. Chrome has started supporting both, will move to unified plan by default soon and expects to completely drop support for Plan B by 2019. https://bugs.chromium.org/p/chromium/issues/detail?id=465349 Testing: https://groups.google.com/forum/#!searchin/discuss-webrtc/unified-plan$20plan-b%7Csort:date/discuss-webrtc/x8lcqHRlWmA/2ycvCHE4AwAJ The following email provides their expected timeline: https://groups.google.com/forum/#!searchin/discuss-webrtc/unified$20plan%7Csort:date/discuss-webrtc/9mVuJ7g3vgs/0yCYoRoxBAAJ "End of April 2018: “Unified Plan” and the new APIs stabilizes. We encourage everyone to switch to UnifiedPlan semantics and the new APIs. July 2018: Default SdpSemantics changes to UnifiedPlan. APIs listed under “Removed APIs” (except CreateSender) are removed at the same time. No earlier than end of year 2018: PlanB semantics removed and UnifiedPlan becomes the only option." 1429171 1 cwehrung 2018-06-01 01:29:32 -0700 Chrome spec: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/Qgwfl-nD0Zs 1430384 2 fippo 2018-06-06 01:42:55 -0700 the timeline in that post turned out to be somewhat unrealistic (in particular given that this would have interop impact with Safari). https://webrtc.org/web-apis/chrome/unified-plan/ has a more up-to-date timeline.