- From: Bramus via GitHub <noreply@w3.org>
- Date: Thu, 04 Dec 2025 11:05:48 +0000
- To: public-css-archive@w3.org
@marnec In https://cdpn.io/pen/debug/MYyaoOX/0d55ffc6a51d38c8f2b45486e5692c59 I have a demo that is using Scoped View Transitions (test it in Chrome Canary, with Experimental Web Platform Features enabled). When clicking one of the “Add+” buttons on the items, that item gets added to the sidebar on the right. As items get added/removed, I would assume that the sidebar itself should also nicely animate along with it. Self-participating scopes allow that, and I think it would be good default to have. I also can’t run the Scoped VT on a parent like you suggest, because the parent of the `#sidebar` is the `<body>`. Scoping it to the `<body>` would prevent me from successively clicking more “Add+” buttons while that VT runs (unless I do some `pointer-events` magic, but Scoped Transitions is meant to solve that for you). Running it on the parent would also prevent me from doing the filter option (top left) as that runs a _concurrent_ VT on the `<main>` (applying the filtering) and the `#sidebar` (updating the weather data). These both share the same parent (i.e. the `<body>`), so there would be a conflict. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12319#issuecomment-3611568732 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 December 2025 11:05:49 UTC