- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Mar 2024 22:16:44 +0000
- To: public-css-archive@w3.org
> And also why use the nearest scroll container instead of the viewport, what happens if the scroll container itself is offscreen. Would love to get a common definition of whether an element is onscreen since VT needs the same concept. What we want is that the element is clipped away "entirely", by some combination of overflow clip rects (and maybe other clipping operations?). This should include all the scroll containers up to the nearest inclusive ancestor of the positioned element's own containing block, at least; higher than that and you're already guaranteed that both elements are getting clipped by the same scroll container, so there's no need to specially care about them. As for what precisely to consider "the box" that is getting clipped, I agree we should defer to what IO/etc are doing for consistency. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7758#issuecomment-1998572752 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 14 March 2024 22:16:45 UTC