- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 17 Jul 2020 18:55:00 +0000
- To: public-webrtc-logs@w3.org
I think these are valid concerns. There's also a precedent here in [latencyHint](https://webaudio.github.io/web-audio-api/#dom-audiocontextoptions-latencyhint). Following that model we could imagine:
```js
enum RTCRtpReceiverLatencyCategory {
"balanced",
"interactive",
"playback",
};
partial interface RTCRtpReceiver {
attribute (RTCRtpReceiverLatencyCategory or double) playoutDelay;
};
```
This should be more web compatible, and remove the onus on web developers to discover the [minimum allowed delay](https://w3c.github.io/webrtc-extensions/#dfn-minimum-allowed-delay) of each browser and work around it with tables of different values for well-known browsers.
Happy to bikeshed enum names based on use-cases. This should also hopefully produce a healthy discussion of what the default value should be (presumably web conferencing is `"interactive"` not `"balanced"`, right?)
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/46#issuecomment-660283609 using your GitHub account
Received on Friday, 17 July 2020 18:55:01 UTC