- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Apr 2024 07:59:40 +0000
- To: public-css-archive@w3.org
> After the capture is done, we can throttle and do the same thing as we do with other CSS animations: run them eventually The downside here though is that we keep snapshots cached which is unnecessary memory for offscreen content. It also involves forcing rendering of offscreen content. https://github.com/w3c/csswg-drafts/issues/8282 could help with it but it's an opt-in. And it seems unfortunate to allow an iframe (potentially cross-origin) to slow down the main frame even when its offscreen because they didn't use this optimization. My inclination here is to skip the transition if the iframe goes offscreen, similar to visibility. With some UA defined margin around the viewport to decide whether its offscreen in case scrolling brings it onscreen while the update callback is running. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9839#issuecomment-2044380496 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 April 2024 07:59:41 UTC