- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Jun 2024 15:25:46 +0000
- To: public-css-archive@w3.org
> avoiding a fly-in that is "quite far" but the element still intersects the viewport by a single pixel IIUC the farthest animation distance in this case would be animating from 1 edge of the viewport to the other (for the longer axis). I was assuming that is not the case authors are trying to fix in that, the element is in the viewport throughout the animation. It's the cases where the element stays offscreen for majority of the animation that looks awkward. Because then instead of getting an animation, the element just "shows up" in the last few frames of the animation. I could very likely be missing an edge case! The other reason I like this proposal is that it makes it trivial for authors to optimize away forced rendering of offscreen content that VT currently does. But the property has to be useful in most cases for authors to actually use it. So definitely happy to get more feedback on whether this actually addresses the target use-cases! -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8282#issuecomment-2161045084 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 June 2024 15:25:46 UTC