- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Nov 2023 23:37:12 +0000
- To: public-css-archive@w3.org
One of the open questions for this feature is defining when an element is considered visible. There's 2 aspects to it: - Intersection with the viewport (snapshot root from VT perspective). Ideally we'd use the element's ink overflow rect for it. IntersectionObserver already uses ink overflow rect to detect occlusion [here](https://w3c.github.io/IntersectionObserver/v2/#:~:text=Implementations%20should%20use%20the%20ink%20overflow%20rectangle%20of%20page%20content%20when%20determining%20whether%20a%20target%20is%20occluded). And #8649 is in progress to make the ink overflow bounds interoperable. - Occlusion by other elements on the page. I haven't seen a use-case where a named element was occluded so I don't know if we need to consider it. Occlusion calculations are also more expensive so better if we can avoid it. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8282#issuecomment-1813465071 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 November 2023 23:37:14 UTC