- From: Bramus via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Jun 2024 19:03:52 +0000
- To: public-css-archive@w3.org
> To me, it sounds like scoped element transitions would be the better solution to this problem. That doesn’t work for websites with a tree of custom elements. In https://divicards-site.pages.dev/ for example the author has a `<e-divination-card>` custom element that they want to transition from the overview to the detail page. The value for `view-transition-name` gets set on the fly on the first div of that component, which seems pretty logical to me. Even if they did set that `view-transition-name` on the `<e-divination-card>` directly it wouldn’t work, because that element itself is a child of another custom element: ``` <app-root> <p-home> <e-card-with-sources> <e-divination-card></e-divination-card> </e-card-with-sources> </p-home> </app-root> ``` -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10145#issuecomment-2174221840 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 17 June 2024 19:03:53 UTC