- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Jul 2022 22:50:26 +0000
- To: public-css-archive@w3.org
> I may be missing something, but isn't that better served by using an IntersectionObserver? In the sense that you presumably don't want to continue making visual-only updates for elements that are offscreen but focused or highlighted. Which is the behavior with IntersectionObserver already - and in order to achieve this with the new event you'd need to track those states and exempt those elements. A focused or highlighted element that is offscreen is much more likely to be brought onscreen sometime soon, and therefore it's a good idea for the developer to keep its canvases up to date. -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7384#issuecomment-1184966445 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 14 July 2022 22:50:28 UTC