- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Nov 2022 19:10:03 +0000
- To: public-webrtc-logs@w3.org
> Was a conscious decision made by this WG, for inherent properties to be capabilities? It is deeply ingrained in the [model](https://w3c.github.io/mediacapture-main/#constrainable-interface): _"The core concept is the Capability, which consists of a constrainable property of an object and the set of its possible values, which may be specified either as a range or as an enumeration. For example, a camera might be capable of framerates (a property) between 20 and 50 frames per second (a range) and may be able to be positioned (a property) facing towards the user, away from the user, or to the left or right of the user (an enumerated set). The application can examine a constrainable property's supported Capabilities via the getCapabilities() accessor."_ I don't recall a challenge related to carving out an exception for inherent properties, but there have been many meetings and CfCs since [2013](https://github.com/w3c/mediacapture-main/commit/993a5af6ab0fdc2123339a80922d10782a0dd254) so this is definitely on purpose and decided. I encourage you to do further research. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/915#issuecomment-1304037942 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 November 2022 19:10:14 UTC