- From: Brian Grinstead via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Jul 2022 18:41:04 +0000
- To: public-css-archive@w3.org
Agreed that the event should map to the content-visibility semantics of relevance, and I can see where it would be beneficial for i.e. focused offscreen elements to be included. Though I don't know if that's what developers actually want for certain use cases like virtual scrollers. For example if a virtual scrolled element is big enough for 10 rows, and a user focuses a text field in a row 1, then scrolls down to row 20 - would that mean that the DOM now has row 1 followed by rows 20-29? If so, is that desireable? I don't know enough about how these are implemented to know. -- GitHub Notification of comment by bgrins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7384#issuecomment-1183555678 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 July 2022 18:41:06 UTC