- From: Nick Coury via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Aug 2023 23:31:23 +0000
- To: public-css-archive@w3.org
Those sound like the right primitives for our use cases, and the second bullet point comment sounds like the same use case. If I'm thinking about use cases that this wouldn't cover, an in-page non-layered and non-navigational RecyclerView comes to mind for infinite scrolling or carousels. I can think of some native app experiences that have infinite content consumption where this might use more flexibility, though I think there are better currently buildable solutions without this complexity, including content-visibility and just regular scrollable containers plus intersection observers so not a great example. For the last use case, we sometimes use intersection observers to do some pre-work for animations to respect RAIL responsiveness guidelines. If we wait for a click to do certain operations needed for animation, it can sometimes take over 100ms on slower devices. We might choose to opportunistically run preprocessing for viewport elements to optimize this which can't be done for multiple possible transitions at a time with VT API. -- GitHub Notification of comment by nickcoury Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8830#issuecomment-1684548261 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 August 2023 23:31:25 UTC