- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Oct 2022 13:09:02 +0000
- To: public-webrtc-logs@w3.org
So, I've tried to accommodate this one more round of spec-shape comments. Hopefully we can agree that this is enough for v1, or something very close to it. > * Rename [InitialFocusLost]] to [[Disabled]] or [[FocusChangeDisabled]] for clarity. I've gone with [[FocusChangeDisabled]] because [[Disabled]] would refer to future APIs too, and we don't intend that atm. > * 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. That's already in the spec - see section with "When the top-level document loses focus, run the following steps on all {{CaptureController}} objects", noting that it's no-op before calling gDM(controller). > * Mention that UAs may decide to set [[Disabled]] based on other heuristics. I've added that. > * Update the finalise focus decision algorithm to call focus on either the capturing surface or the captured surface based on [[FocusBehavior]]. I don't think focusing the capturing surface is desirable. It could interfere with the users own actions, and cannot otherwise help. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/pull/240#issuecomment-1277583231 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 13:09:03 UTC