- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Jun 2024 16:36:14 +0000
- To: public-css-archive@w3.org
We would then have a common root from which to reference the transform. There's still work to recompute the old transform by accumulating ancestors until the new root, which should all be available as well. The new transform would also be relative to this element, which makes the animation make sense I guess we'd miss something like an ancestor filter on a group but that's probably not a common effect. I'm trying to weigh this solution to another one where the old state would keep the old image and the new state would keep the new image and have the transform there (I forgot who proposed this in an internal sync, apologies). The duplicating approach seems complicated and also doesn't solve all of the use cases (mix-blend-mode: plus-lighter for e.g.) All in all, I'm happy with lowest common ancestor approach -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10334#issuecomment-2173859500 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 16:36:15 UTC