Bug 1631263 Comment 11 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Just to update this issue that the plan is to implement the latest spec, which is [RTCRtpScriptTransform](https://w3c.github.io/webrtc-encoded-transform/#scriptTransform), and not any previous Chrome API. This is the API we'd implement that most matches the requests from major services. 

Separately, the spec also offers am [SFrameTransform](https://w3c.github.io/webrtc-encoded-transform/#sframe) API, which would provide sframe encoding natively without requiring this to be done by JS. This API is a bit less mature, and we haven't gotten requests for it yet. I'll open a separate issue on that.
Just to update this issue that the plan is to implement the latest spec, which is [RTCRtpScriptTransform](https://w3c.github.io/webrtc-encoded-transform/#scriptTransform), and not any previous Chrome API. This is the API we'd implement that most matches the requests from major services. 

Separately, the spec also offers the [SFrameTransform](https://w3c.github.io/webrtc-encoded-transform/#sframe) API, which would provide sframe encoding natively without requiring this to be done by JS. This API is a bit less mature, and we haven't gotten requests for it yet. I'll open a separate issue on that.

Back to Bug 1631263 Comment 11