- From: Marco Necci via GitHub <noreply@w3.org>
- Date: Thu, 04 Dec 2025 08:58:19 +0000
- To: public-css-archive@w3.org
I premise that my understanding is limited and I did not look at the source code. Please, correct me if anything wrong was said in this post. In the doc @skobes-chromium says "It's natural to want the scope itself to be a participant in its own transition, like this:" I don't think this is necessarily true, meaning I don't see as necessarily natural that the container (scope) would participate in the animation. I find it more intuitive and ergonomic that "container" and "animated element" remain separate concepts. I can't imagine a use-case where you'd absolutely need a scope to be self-participating. If a view transition needs to be applied to a scope, it could be wrapped in a parent scope, with the root scope being `document`. If I understand correctly, `document` wouldn't (and couldn't) be self-participating anyways and having other scopes being self-participating would create an inconsistent scope behavior. -- GitHub Notification of comment by marnec Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12319#issuecomment-3610964112 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 08:58:20 UTC