- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Aug 2019 21:18:29 +0000
- To: public-webrtc-logs@w3.org
On `getDisplayMedia` yes, but `track.applyConstraints` still works.
This doesn't matter as long as [displaySurface](https://w3c.github.io/mediacapture-screen-share/#dom-mediatracksettings-displaysurface) and [logicalSurface](https://w3c.github.io/mediacapture-screen-share/#dom-mediatracksettings-logicalsurface) remain constant.
>I'm not convinced we should enforce these being constants,
If they can change, we'd need to figure out what happens if JS succeeds at locking them. E.g.:
```js
await track.applyConstraints({displaySurface: {exact: "browser"}); // say this succeeds
```
Should this bar the user agent from switching to a non-"browser" source?
FWIW I don't see a use-case that requires these to be variable. Implementing an "active tab" source doesn't seem impeded by keeping these constant.
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/81#issuecomment-517847252 using your GitHub account
Received on Friday, 2 August 2019 21:18:30 UTC