- From: Rémi Scandella via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 Jul 2024 20:21:12 +0000
- To: public-css-archive@w3.org
If I may mention my own use case here: my team is working on an app built entirely with web components, so we have nested components with shadow roots. Chrome 126 broke our View Transitions. Enabling `view-transition-name` on `::part` would be a useful solution if we also had scoped View Transitions. Starting a View Transition on a deeply nested custom element, then giving names to its sub-components with `::part` sounds doable. But without scoped View Transitions, we'd have to use the `exportparts` attribute all the way up to the document element, since that's the only element we can start a View Transition on right now, right? That sounds very impractical. A solution like a CSS attribute, as mentioned [here](https://github.com/w3c/csswg-drafts/issues/10145#issuecomment-2175638968), looks like it would help us a lot more in that case. -- GitHub Notification of comment by Remiscan Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10145#issuecomment-2200955485 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 1 July 2024 20:21:13 UTC