- From: Chris Harrelson via GitHub <noreply@w3.org>
- Date: Mon, 29 Sep 2025 21:33:04 +0000
- To: public-css-archive@w3.org
> It doesn't? Safari does it during the style / layout loop afaict. Blink does do it during the loop, via special internal versions of `IntersectionObserver`, like I mentioned above (that's what kDeliverDuringPostLayoutSteps does). > But that's not what the spec says to do (that accounts for a lot more than scrolling overflow, like overflow: clip, clip-path, etc). Hmm I think you're right, sorry about that. So consistency with `IntersectionObserver`'s notion of clipping (which includes clip-path and so on) is an advantage. Upon further reflection, I actually prefer not having to implement and optimize a whole new code path that will be hot during scroll intersections. A lot of effort went into optimizing `IntersectionObserver`. -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12732#issuecomment-3349130445 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 29 September 2025 21:33:05 UTC