- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Tue, 25 Oct 2022 19:05:42 +0000
- To: public-webrtc-logs@w3.org
This is to abide by the [constrainable pattern](https://w3c.github.io/mediacapture-main/#capabilities) where capabilities give you the envelope of available inputs to applyConstraints, so this helps inform that this property is [inherent](https://w3c.github.io/mediacapture-main/#list-of-inherent-constrainable-track-properties) to the source and not changeable through applyConstraints. > Note that it was added in https://github.com/w3c/mediacapture-screen-share/pull/84 It's worth noting that at the time of that PR the source couldn't change. Now that we allow source switching in screen-capture, we should check whether this conflicts with mediacapture-main at all: From a cursory glance, it looks OK to me: The description of [capabilities](https://w3c.github.io/mediacapture-main/#dfn-capabilities) says _"Source capabilities are effectively constant. Applications should be able to depend on a specific source having the same capabilities for any browsing session."_ This ties capabilities as constant to the source, which I think can be read to support them changing when the source changes. So we may be good here and not require any new spec language. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/250#issuecomment-1291014296 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 25 October 2022 19:05:44 UTC