- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Aug 2024 15:34:32 +0000
- To: public-css-archive@w3.org
> > My current thinking is that "last capture wins" is the simplest and more consistent with existing stuff > > By "last capture wins" I think you mean we use the ancestor based on the new DOM? How do we deal with a case where the new element uses an ancestor which is not in the old element's ancestor chain? We have to figure out what the old transform should be in this case. The old element will save the final transform, and we'll project to be relative to the final parent. > I'm not opposed to this idea but stuff like the above seems easier to reason about with "least common ancestor". Since you can always map the cached old transform to any ancestor. The fallback is more like the default flat mode. Is there more stuff like the above? -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10631#issuecomment-2273758953 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 August 2024 15:34:32 UTC