- From: szager-chromium via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Mar 2024 18:08:14 +0000
- To: public-css-archive@w3.org
@jfkthame Those are legitimate concerns with respect to IntersectionObserver V2. If UA settings or accessibility features cause an element of interest to be occluded, then the correct behavior is for V2 to report the content as "possibly occluded". I think it's a good idea to for the spec to call out these issues in non-normative text, but I would lean towards adding it to the IntersectionObserver spec. I still think it's worth exploring whether there is some language we can add to css-text that is helpful to developers and relevant to non-IntersectionObserver use cases. Including caveats such as "for a given well-defined font" allows this change to be focused on the behavior of the glyph rendering subsystem without involving other parts of the spec or the browser. -- GitHub Notification of comment by szager-chromium Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8649#issuecomment-2013202812 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 March 2024 18:08:15 UTC