- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Mar 2023 14:39:11 +0000
- To: public-webrtc@w3.org
jan-ivar has just created a new issue for https://github.com/w3c/mediacapture-main: == Clarify the type of Constrainable Properties == This spec still conflates _constraints_ and _constrainable properties_ in places (the former are applied to the latter). One instance is its description of _types_ of [constrainable properties](https://w3c.github.io/mediacapture-main/#constrainable-properties) (skip `deviceId` and `groupId` for now due to https://github.com/w3c/mediacapture-main/issues/941, and skip integer ones due to https://github.com/w3c/mediacapture-main/issues/944): ![image](https://user-images.githubusercontent.com/3136226/227971979-9d3a5cb7-e85d-43f2-9b41-528de45f7c89.png) This is wrong and misleading. The type of the constrainable property, the property being constrained on, is a simple type, not a Constrain* dictionary. E.g. the _type_ of the _constrainable property_ [frameRate](https://w3c.github.io/mediacapture-main/#dfn-framerate) is [double](https://w3c.github.io/mediacapture-main/#dom-mediatracksettings-framerate), not [ConstrainDouble](https://w3c.github.io/mediacapture-main/#dom-constraindouble). This didn't used to matter, but with https://github.com/w3c/mediacapture-main/pull/766 it is causing confusion, e.g. in https://github.com/w3c/mediacapture-main/issues/933. Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/945 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 27 March 2023 14:39:13 UTC