- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Oct 2022 08:58:07 +0000
- To: public-webrtc-logs@w3.org
> @youennf, I have intentionally shaped the PR to be no-op for your case. This makes this whole API useless for these UAs, meaning it will not be implemented. It also casts doubts on the actual API design if it can only accommodate one single selection picker model. > could you please suggest a concrete change How about the following: - Rename [InitialFocusLost]] to [[Disabled]] or [[FocusChangeDisabled]] for clarity. - Make the controller listen to loss of page focus at the time the promise is resolved. If page already lost focus at this point, the controller remains active except if the page regains focus and loses it again. - Mention that UAs may decide to set [[Disabled]] based on other heuristics. - Update the finalise focus decision algorithm to call focus on either the capturing surface or the captured surface based on [[FocusBehavior]]. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/pull/240#issuecomment-1277272447 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 October 2022 08:58:09 UTC