- From: François Beaufort via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Nov 2022 08:20:21 +0000
- To: public-webrtc-logs@w3.org
Going back to `displaySurface`, I'm not sure what would be the difference between returning an array of a unique string value and a unique string value. Both can't be changed later with applyConstraints.
```js
// Current situation
console.log(track.getCapabilities().displaySurface); // "monitor", "window", or "browser"
```
```js
// New ?
console.log(track.getCapabilities().displaySurface); // ["monitor"], ["window"], or ["browser"]
```
```js
// This is no-op either way as the displaySurface can't be changed later.
await track.applyConstraints({displaySurface: {exact: "browser"}});
```
In that case, does it make sense to expose the `displaySurface` capability at all? It seems like it goes down to this "make sense" part. I'm not sure either ;)
--
GitHub Notification of comment by beaufortfrancois
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/915#issuecomment-1303105822 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 08:20:23 UTC