Re: [webrtc-pc] Make legacy API optional to implement

In WebKit, these legacy methods are implemented but some are not aligned with the spec.
WebKit might probably end up not supporting them.

Keeping those APIs in the spec has a cost for implementations (code, testing), the spec itself (already quite large) and users (nicer APIs available anyway).
That seems like a healthy move to try deprecating them by either removing or making them optional.

I am all for a place where legacy APIs would be described in terms of the spec APIs.
For instance onaddstream seems to be quite in use by some web sites and is not described in the spec AFAIK. Such a description could be written in a separate spec or as a JS shim.

GitHub Notification of comment by youennf
Please view or discuss this issue at using your GitHub account

Received on Thursday, 23 March 2017 17:31:21 UTC