- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Apr 2024 19:47:44 +0000
- To: public-css-archive@w3.org
At [this point](https://drafts.csswg.org/css-view-transitions-1/#capture-old-state-algorithm:~:text=Set%20capture%E2%80%99s%20old%20image%20to%20the%20result%20of%20capturing%20the%20image%20of%20element.) in the algorithm when we cache the old state, we just know that the named element in the old DOM is offscreen. We don't yet know if its corresponding named element in the new DOM will be onscreen. And when we get to new state steps, the old DOM has already been replaced by the new DOM. I could imagine an optimized implementation internally preserves a cheap copy of the old DOM; such that generating an image of the old DOM elements can be deferred until the browser knows what the new DOM looks like. And skip rendering/caching the image if the new state is offscreen without any web observable effects. Hmmm, can webkit do this? :) -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8282#issuecomment-2045941029 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 19:47:45 UTC