[webrtc-pc] Legacy Interface Extensions is somewhat unclear (#3027)

gsnedders has just created a new issue for https://github.com/w3c/webrtc-pc:

== Legacy Interface Extensions is somewhat unclear ==
https://w3c.github.io/webrtc-pc/#legacy-interface-extensions opens with:

> Supporting the methods in this section is optional. However, if these methods are supported it is mandatory to implement according to what is specified here.

It then defines various "method extensions": these are just defining behaviour for given operation overloads — I don't think it is intended that `RTCPeerConnection` interface's `createOffer` operation is optional to support, just that that specific overload is optional to support.

It's also to me somewhat unclear whether this text allows you to support the legacy `createOffer` overload but not the legacy `setLocalDescription` overload; i.e., can you support _some_ of the legacy overloads, or is it meant to be all or nothing? They're optional, but is that collective or individual — the second sentence quoted above makes me think the intention is collective, but it could be clearer.

Then we reach the "Legacy configuration extensions" — and here it is very unclear what the implementation requirement is. Dictionary members are in no way methods, and the `createOffer(optional RTCOfferOptions options = {})` override is mandatory to implement, so it doesn't obviously fall under the "supporting the methods in this section", which… implies supporting them is mandatory? But I don't think that's the intention.

We should clarify the conformance requirements for this section.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3027 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 6 December 2024 00:59:12 UTC