- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Sep 2023 14:33:42 +0000
- To: public-webrtc-logs@w3.org
I think the spec guidance [is there](https://w3c.github.io/mediacapture-main/#dfn-capabilities): _"For each constrainable property, there is a capability that describes whether it is supported by the source and if so, the range of supported values"_. > Chrome sets it to `[]`. I can repro with https://jsfiddle.net/jib1/3gpy9ndz/ — The constraints concept being a triad, my takeaway is one of the intended invariants is that any value exposed in either getSettings or getCapabilities also appears in the other. It seems a bug to surface a value in only one of getSettings and getCapabilities. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/969#issuecomment-1725767776 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 September 2023 14:33:44 UTC