- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Nov 2022 20:18:27 +0000
- To: public-webrtc-logs@w3.org
I'm not really following you. The question of sequence-of-one seems orthogonal to the question I am trying to raise. Let me repeat my proposal differently. I am proposing that: - Properties that can **theoretically** be changed in a spec-compliant way by calling applyConstraints(), should be a capability with the range/set of legal values. - If on the **current track** the range/set consists of more than a single value, everything is clearly defined right now. - If on the **current track** the range/set consists of a single value, we run into the question of `"value"` vs. `["value"]`. That's an orthogonal question. If you wish to discuss it, let's do so separately. - Properties that cannot ever be changed, not even theoretically, should not be a capability. Examples include `displaySurface`. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/250#issuecomment-1302619315 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 November 2022 20:18:29 UTC