- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Jun 2024 13:58:56 +0000
- To: public-css-archive@w3.org
@fantasai, the topology thing I was talking about is this: Consider this old state: <img width="301" alt="Screenshot 2024-06-13 at 9 50 01 AM" src="https://github.com/w3c/csswg-drafts/assets/1906955/413e573c-6499-416b-8728-34f477d50971"> And this new state: <img width="383" alt="Screenshot 2024-06-13 at 9 50 12 AM" src="https://github.com/w3c/csswg-drafts/assets/1906955/9ada6bbf-68ee-4cb0-8255-284ff1647ee0"> It's pretty clear that the pseudo here should provide (and it's similar to the new state) where things nest under another. But now consider a different old state: <img width="401" alt="Screenshot 2024-06-13 at 9 50 06 AM" src="https://github.com/w3c/csswg-drafts/assets/1906955/bfa745e8-183c-4a20-8e15-25a6b6a3fa18"> With the same new state. This should produce a different pseudo tree, because the common ancestor is different. However, if we only keep the vt tree, we don't have that information Unless you meant "common ancestor" only in the vt pseudo tree sense -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10334#issuecomment-2165759665 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 June 2024 13:58:57 UTC