- From: Noah Lemen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Jul 2022 17:18:31 +0000
- To: public-css-archive@w3.org
This is definitely crucial for being able to leverage `content-visibility:auto` to replace userland implementions of virtual scrollers. For example, in our JS-based virtual scroller on Facebook, we use intersection observers to determine visibility – we then use this to control both rendering of the elements, as well as to flag these React components for deprioritized updates. When attempting to use `content-visibility:auto` to replace this implementation, we currently lose out on the latter. We certainly _could_ continue to use an intersection observer for this aspect of the functionality, but I think that is undesirable for the reasons @chrishtr mentioned. -- GitHub Notification of comment by noahlemen Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7384#issuecomment-1182039257 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 12 July 2022 17:18:33 UTC