- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Feb 2023 16:01:37 +0000
- To: public-webrtc-logs@w3.org
guidou has just created a new issue for https://github.com/w3c/mediacapture-main: == Fitness distance steps 4 and 5 are inconsistent with the rest of the spec == Steps 4 an 5 refer to settings dictionaries as if they were IDL dictionaries, having members. But settings dictionaries are not IDL dictionaries and their internal structure understood to be an implementation detail elsewhere in the spec. The spec explicitly says `We use the term settings dictionary for the set of values that might be applied as settings to the object.`, which does not necessarily translate to they working like IDL dictionaries with explicit members that might or might not be present. Another problem is that step 4 says `If constraintValue is a boolean, but the constrainable property is not`, which sounds impossible in IDL. I understand that this is intended to support pan/tilt/zoom constraints which accept boolean and numeric values. These constraints are of type (boolean or ConstraintDouble), so the constraint value is compatible with the property. One way to make this clearer is to treat this particular constraint type separately, just like purely numeric constraints are treated separately from purely boolean/enum/string constraints. Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/933 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 27 February 2023 16:01:39 UTC