- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Jan 2024 15:24:23 +0000
- To: public-css-archive@w3.org
khushalsagar has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-view-transitions-1] Handle startVT for offscreen iframes == It's unclear what should be done when an iframe is offscreen and rendering opportunities for it are throttled, see spec for that state [here](https://html.spec.whatwg.org/#:~:text=Remove%20from%20docs%20all%20Document%20objects%20for%20which%20the%20user%20agent%20believes%20that%20it%27s%20preferable%20to%20skip%20updating%20the%20rendering%20for%20other%20reasons) : "Remove from docs all [Document](https://html.spec.whatwg.org/#document) objects for which the user agent believes that it's preferable to skip updating the rendering for other reasons". It's unclear how ViewTransitions should be handled in this state. Suppressing rendering opportunities implies that the behaviour differs based on when that happens. If its before the old state was snapshotted, we'd hit a timeout and abort the transition. If its after the pseudo-DOM was setup, then its similar to the author starting CSS animations on an offscreen Document. It's probably better to have consistent behaviour here. The decision for this should likely also influence scoped transitions? If the root element of that transition is offscreen for example. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9839 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 January 2024 15:24:26 UTC