- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Apr 2024 14:24:52 +0000
- To: public-css-archive@w3.org
vmpstr has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-anchor-position-1] Clarify interaction of anchors and positioned elements with content-visibility == In #10040 we've resolved that > ... if a positioned element is "relevant to the user", any element it's anchoring to remains "relevant to the user" as well. This particular phrasing poses some implementation difficulties, since we don't typically track whether an arbitrary element is relevant to the user. We only tend to do that in the context of its effect on `content-visibility`. I think this should say the following: > if a positioned element is **not skipped**, any element it's anchoring to remains "relevant to the user". since being skipped is something that is imposed on the element by `content-visibility`. This does mean that if the anchor and the positioned elements are both off-screen, but the positioned element is not under `content-visibility`, then the anchor will remain relevant to the user. I think that's fine though. As an aside, I presume that if the positioned element is display: none or something, then it's not actually a positioned element and thus is not anchoring to the anchor /cc @tabatkins @progers @mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10184 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 April 2024 14:24:53 UTC