- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Jun 2024 07:55:42 +0000
- To: public-css-archive@w3.org
> One of our public-facing apps at Microsoft was also broken by this change. Our app is built entirely with web components; a tree of web components with shadow roots. > > In our case, when the user navigates our SPA, we want to view transition everything except that header and footer. So we assigned those a separate `view-transition-name`. This worked until Chrome 126. > > We'd love a way to say, "this web component has a different view-transition-name" so that it can remain in place during view transitions. I don't feel strongly about any of the proposals so far. So long as we can do what we did before: give elements different view-transition-names so they don't take part in view transition. So if I understand correctly, the issue here was not about mixing light-DOM elements with shadow-DOM elements, but rather that all the elements participating were inside the shadow DOM, and now this can't work? -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10145#issuecomment-2196350727 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 June 2024 07:55:43 UTC