- From: jimmy-guo via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Apr 2025 20:03:57 +0000
- To: public-css-archive@w3.org
>The behavior of the old position being fixed is a consequence of the fact that we need to support cases where the "old" element is gone. It might have been affected by the scroll, or might have been in a different scroller, or be fixedpos. I would claim that this is intentional. > But our implicit assumption was that interactions like scrolling won't happen during the transition since its a transient state for animations and the pseudo-elements consume all the events (via the default UA CSS). If that doesn't work for a use-case, I'd be happy to hear the details and see if we can do anything better. Hi @khushalsagar @vmpstr, exploring options here: Would it be possible to support a configuration to set the desired behavior? My use case is that I have a list on Page A. Clicking on one of those list items transitions to Page B and does an expansion animation where one image expands into several. (There is 1 shared element transition between Page A and B; the remaining image elements are net new). When I click "back" to navigate back to page B, the reverse of the animation happens where the previously net new images collapse behind the original image. However, because the list on Page A is long, I would like to restore scroll to that list item. Unfortunately, while that works for the shared element transition, the remaining images continue to use their stale positioning and fly off the bottom of the page. -- GitHub Notification of comment by jimmy-guo Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10197#issuecomment-2840107787 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 April 2025 20:03:58 UTC