- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Feb 2024 19:49:33 +0000
- To: public-css-archive@w3.org
> The spec currently says that the anchored element position is determined as if all of the scrollers are scrolled to the top. The scrolling adjustment is then made by a snapshot scroll offset. I think this works fine for the common scrolling case. This sounds like the implementation details. Is this actually developer observable in a meaningful way? I think as far as a developer is concerned it determines the necessary offset to align the anchor - similar to sticky position. The general direction we have been thinking with scroll driven animations is that authors can do bad things, however in the majority of cases we want animations to work as expected. As such, I'd expect it to use the current animation values. However, similar to sticky position and view timelines, we would use the non-transformed box, which allows authors to implement transform effects without them interfering and also means we don't have to worry about things like rotations or perspective. Often this allows authors to implement cool effects by using transforms in interesting ways without it interfering with the positioning. Similar to sticky position - see #8298, we may want to adjust some of the view timeline animation ranges to account for anchor offsets. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9379#issuecomment-1965132748 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 February 2024 19:49:34 UTC