Are there any usecounters indicating usage? (Or another method of estimating potential breakage)
On Friday, September 4, 2026 at 12:21:47 PM UTC+2 Chromestatus wrote: > *Contact emails* > [email protected] > > *Explainer* > *No information provided* > > *Specification* > https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection > > *Summary* > This is a legacy and obsolete method that does not exist in the WebRTC > spec and the only major engine implementing it is Blink. Removing it is > part of Interop 2026. > > *Blink component* > Blink>WebRTC>PeerConnection > <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EWebRTC%3EPeerConnection%22> > > *Web Feature ID* > webrtc <https://webstatus.dev/features/webrtc> > > *Motivation* > This is a legacy and obsolete method that does not exist in the WebRTC > spec and the only major engine implementing it is Blink. Removing it is > part of Interop 2026. > > *Initial public proposal* > *No information provided* > > *Goals for experimentation* > None > > *Debuggability* > N/A > > *Requires code in //chrome?* > False > > *Tracking bug* > http://crbug.com/553274713 > > *Measurement* > https://chromestatus.com/metrics/feature/timeline/popularity/1642 > > *Estimated milestones* > Shipping on desktop 160 > Shipping on Android 160 > Shipping on WebView 160 > > *Link to entry on the Chrome Platform Status* > https://chromestatus.com/feature/5160724576993280?gate=5985122343059456 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com>. > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/20f127ef-55bf-465a-9907-9d29d26fc401n%40chromium.org.
