- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Jun 2023 18:17:50 +0000
- To: public-css-archive@w3.org
@ydaniv thanks for clarifying. Do you mind updating the issue title? It doesn't sound like we have a perf issue. It's having to leak information from a component triggering/managing the transition to the embedding context. Also updating the label since this seems like a future feature request but not an issue that needs to be fixed in the current spec. FWIW, I feel like involving the root (or embedding page) for transitions which span the entire Document makes sense. The whole Document is going to be paused with a layer (view transition stacking context) on top of the whole Document. So a component trying to do it transparently, i.e, avoiding setting state on the documentElement doesn't make sense. It is a valid question for [scoped transitions](https://github.com/WICG/view-transitions/blob/main/explainer.md#transitions-targeted-to-a-specific-element). But assuming the whole setup (like the view transition stacking context) is scoped to the element which is the root of the transition (and thus the originating element for all pseudos associated with that transition), you could do the class based approach by targeting the element which is the root of that transition. This is conceptually similar to how a transition in an iframe would work. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8960#issuecomment-1599284540 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 20 June 2023 18:17:52 UTC