- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Mon, 22 Dec 2025 22:31:55 +0000
- To: public-css-archive@w3.org
Agreed about requiring a non-zero intersection area *when* the anchor's own area is non-zero. (If you have a zero-width/height anchor, it's okay for it to be considered visible when it's on the edge.) For the "both anchor and anchorpos have the same CB" case, yes, that's intended behavior. anchors-visible is meant to avoid the situation where your anchor scrolls away in a scroller below your CB; you don't want to hang out in space "attached" to nothing visible. If you both have the same CB, then any "scrolling away" will hide both you and the anchor equally, and there's no need to try and hide you just because your anchor has moved out of the scrollport. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13176#issuecomment-3684418712 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 22 December 2025 22:31:56 UTC