- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Apr 2024 15:19:21 +0000
- To: public-css-archive@w3.org
The behavior of targetting the new location of the element is, of course, intentional, since we want to retarget to the new position anytime that changes due to scroll or any other change. The behavior of the old position being fixed is a consequence of the fact that we need to support cases where the "old" element is gone. It might have been affected by the scroll, or might have been in a different scroller, or be fixedpos. I would claim that this is intentional. @noamr I'm not sure what the right spot to add a non-normative note is, but possibly around the capture steps? -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10197#issuecomment-2049945666 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 April 2024 15:19:21 UTC