- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Sep 2021 17:14:56 +0000
- To: public-webrtc-logs@w3.org
> The browser can operate in modes which skip the prompt. That is out of scope for this working group. > The spec may be agnostic of these, but the fact remains that the user can accept multiple different captures within a very short span of time. @eladalon1983 Not a problem. JS is single-threaded, and [getDisplayMedia](https://w3c.github.io/mediacapture-screen-share/#dom-mediadevices-getdisplaymedia) implicitly queues a task to resolve a promise from in parallel steps. My proposal would be to queue two tasks, guaranteed to happen in succession. There is no "span of time" short enough for two `getDisplayMedia` calls resolving to be a problem. > it's a lot more ergonomic to call focus() on the right track, than to to manipulate a global attribute at just the right time, You have to call focus() at just the right time as well. Also, if ergonomics is the issue, why isn't it `stream.focus()`? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/190#issuecomment-928085223 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 27 September 2021 17:14:58 UTC