- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Oct 2021 12:58:08 +0000
- To: public-webrtc-logs@w3.org
> FWIW, as I understand it the task responsible for resolving getDisplayMedia() has been traditionally also the focus task. I ran a test to disprove this https://jsfiddle.net/jib1/q75yb8pf/ but I was also surprised to learn that Firefox blurs the capturer window 15 ms _before_ it resolves the promise (I thought it happened much later): ``` 4823: blurred 4837: resolved ``` But if we're worried about web compat here we have a much bigger problem: Chrome's prompt steals focus. ``` 1827: blurred 16078: resolved ``` We've never specified exactly when (non-browser) window is focused before, and I'm not sure we need to here. What we're specifying here is a JS control opportunity by requiring the browser to fire a warning ping _"hey, I plan to focus another window, you ok with that?"_, which to me doesn't inherently need to match up with any user-visible behavior timing wise. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/190#issuecomment-938622288 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 8 October 2021 12:58:10 UTC