- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Jan 2025 00:01:22 +0000
- To: public-webrtc-logs@w3.org
> I am unsure how much we can enforce this in the spec though. I think we can enforce it in https://github.com/w3c/mediacapture-surface-control/issues/42#issuecomment-2605884420. > - If the capture source of a hidden surface is not producing frames, there is no need to prevent throttling. > - Conversely, generation of frames should prevent throttling. > - If preventing throttling is done, the surface should be considered as visible (specific to UA surfaces probably). This sounds reasonable, except throttling is more of a UA optimization. Can we express it without that? Based on this note in [html](https://html.spec.whatwg.org/multipage/interaction.html#the-visibilitystateentry-interface): <img width="749" alt="Image" src="https://github.com/user-attachments/assets/709f4a20-c666-4bbd-920a-31c166f6177e" /> ...maybe we should express it relative to the document's [visibility state](https://html.spec.whatwg.org/multipage/interaction.html#visibility-state) instead? Happy to review a PR. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/307#issuecomment-2605987192 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 00:01:23 UTC