- From: Martin Trapp via GitHub <noreply@w3.org>
- Date: Fri, 15 May 2026 08:02:50 +0000
- To: public-css-archive@w3.org
Thanks for the detailed reply! Naturally, I would prefer a solution for retargetable view transitions that is directly supported by the API, but I am far too impatient to wait for that. I would have loved the opportunity to experiment with the capabilities already available today, just to gain some experience and explore the boundaries, even if it ended up feeling hacked together. Proper standardised solutions are obviously much nicer. But it is also in the nature of these things that it will take many month before retargetable view transitions become Baseline across all browsers. Just briefly on what I had in mind: to avoid interfering with the existing view transition, I wanted to introduce a new parent and start a new view transition there. I had expected to get access to the image as well as the position and transform of the existing pseudo elements during capture, then terminate the interrupted view transition and continue the new one within the parent. The dynamically inserted parents could then be cleaned up afterwards. It may well be that none of this would actually work, but I cannot even try it out. With a non-!important definition in the UA stylesheet, I actually could. No hard feelings ;-) -- GitHub Notification of comment by martrapp Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13637#issuecomment-4458100915 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 May 2026 08:02:51 UTC