- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Jan 2025 19:04:41 +0000
- To: public-webrtc-logs@w3.org
> There might be implementations in the future that don't capture frames if the window is minimized for instance. I don't think that'd make a difference. The way I see it: 1. All captured tabs are mandated to be "visible" by the [Screen Capture spec](https://www.w3.org/TR/screen-capture/), as per yesterday's interim meeting. 2. No action from CSC can take place on anything other than a captured tab. The combination of (1) and (2) produces "no action from CSC can take place on anything other than a tab whose main document is "visible". What am I missing? > There might also be implementations that try to implement this API to work with both tab and window capture of a browser window. Captured **windows** don't have `document.visibilityState`. Only captured **tabs** have that. **If** we extend this API to support window-capture in the future, and **if** we then choose to give special treatment to captured browser windows (as opposed to treating them as any native window), then we will have to introduce a few new concepts and connections, including the "window's active tab's main page's visibility state", at which point we can indeed add this requirement. But it does not seem helpful now. Or what am I missing? -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-surface-control/issues/42#issuecomment-2608043960 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 January 2025 19:04:42 UTC