- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Jul 2024 16:00:21 +0000
- To: public-webrtc-logs@w3.org
The TAG clarified its design principle last year, which I think applies here: - [ยง 10.2.1. Some APIs should only be exposed to dedicated workers](https://w3ctag.github.io/design-principles/#worker-only) With that I propose we can close this issue. A chromium shim to handle backwards compatibility exists in https://github.com/webrtcHacks/adapter/pull/1145 and was demonstrated to work in https://blog.mozilla.org/webrtc/end-to-end-encrypt-webrtc-in-all-browsers. I'm open to improving it as needed. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/89#issuecomment-2220911219 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 July 2024 16:00:21 UTC