- From: Philipp Hancke via GitHub <noreply@w3.org>
- Date: Fri, 17 Apr 2026 06:34:12 +0000
- To: public-webrtc-logs@w3.org
> https://w3c.github.io/webrtc-pc/#dfn-create-an-rtcrtpreceiver step 2. Thank you. So the interop problem here is that users complain about seeing "remote <kind>" instead of a uuid instead of and services block Firefox and Safari because of that? > given your experience with adapter.js, any additional area we should look for Interop 2026 (or later) that would ease/reduce adapter.js use? adapter is on its way out (despite hitting 2m weekly downloads). Fixing Safari's continued refusal to implement ["legacy" offer options]( https://wpt.fyi/results/webrtc/legacy/RTCRtpTransceiver-with-OfferToReceive-options.optional.https.html?label=experimental&label=master&aligned) despite publically available data showing it it widely used might actually help web developers who don't use it. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3100#issuecomment-4265933964 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 17 April 2026 06:34:13 UTC