- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Oct 2024 21:35:27 +0000
- To: public-webrtc@w3.org
jan-ivar has just created a new issue for https://github.com/w3c/webrtc-extensions:
== receiver.hardwareAcceleration attribute instead of disableHardwareDecoding() static method ==
It doesn't look like `RTCRtpReceiver.disableHardwareDecoding()` has shipped anywhere.
Mozilla feedback in https://github.com/mozilla/standards-positions/issues/728 was originally negative (though a formal position never formed).
But after [recent review](https://github.com/mozilla/standards-positions/issues/728#issuecomment-2427349467), we'd like to propose a slightly different API shape that Mozilla would get behind:
```webidl
partial interface RTCRtpReceiver {
HardwareAcceleration hardwareAcceleration = "no-preference";
}
```
It's a receiver attribute instead of a static method.
Importantly for us, [HardwareAcceleration](https://w3c.github.io/webcodecs/#hardware-acceleration) is defined in WebCodecs, which has a page-long note about when the UA might override webpage preference.
We think this would resolve our concerns raised in the issue, specifically around the UAs ability to override website preference in situations like after a hardware codec fix.
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/229 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 October 2024 21:35:28 UTC