- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Jul 2022 18:23:45 +0000
- To: public-css-archive@w3.org
The intent of the event is to respond to any changes that take the element from being relevant to not being relevant (and vice versa). The polyfill would need to consider selectionchange and possibly other events as well, which I realize I haven't mentioned in the explainer. I'm curious to hear whether the proximity to the viewport is the _interesting_ thing to observe, or it's strictly required that we don't include things like selection (and other relevant-to-the-user aspects) here. As an example, if there is an off-screen selection, then I can see an argument for why one would want that content to be updated since it can always make it into the copy buffer via ctrl/cmd-c or something similar. Similarly some focused elements (text input) support things like ctrl-a ctrl-c to select the text in there regardless of whether or not the element is on-screen. -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7384#issuecomment-1183540432 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:23:47 UTC