- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Nov 2023 13:18:47 +0000
- To: public-css-archive@w3.org
> I think this gets solved appropriately with the exact same solution as https://github.com/w3c/csswg-drafts/issues/8180 - if the tree-scoped reference is resolved as part of the computed value, then having it change underneath you counts as a computed-value change, thus triggering a transition, and the start and end values are (non-textually) distinct, referring to the old and new anchor, so you can meaningfully transition between them. In other words, something _like_ a tree-scoped name, but instead of only capturing the tree-scope, it now also captures the _element_ it's referencing? This means intermediate states would appear to interpolate to and from the same value, when serialized, right? @tabatkins Have we considered resolving `anchor()` computed-value time instead? (Similar to how `cq*` units have layout dependencies, but also resolve computed-value time and can trigger transitions). -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8181#issuecomment-1810189679 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 November 2023 13:18:48 UTC