- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 12 Apr 2024 08:54:28 +0000
- To: public-css-archive@w3.org
A potential perhaps-legit optimization the UA can do is this: - See that a particular URL (or session) consistently marks `view-transition-name` to elements that are never in the viewport - Start not capturing the snapshot for these elements, opportunistically - If this pattern is broken, and one of those elements goes into the viewport, skip this particular transition and turn the optimization off for this URL/session. So you'd have one prematurely skipped transition for the whole session if that ever happened but you'd gain the optimization. However, this type of optimization is a tangent to this discussion. The thing I think we should solve here is - allowing the web developer to decide that for particular view-transition participants, if it's offscreen in one of the phases, the animation should act like an exit/entry transition. "I would prefer this article to fade in rather than to fly from the bottom if it comes from outside the viewport". The only way to achieve this today is by measuring/interscecting with javascript, and IMO it's an important enough use-case to make declarative. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8282#issuecomment-2051325650 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 12 April 2024 08:54:29 UTC