Re: [csswg-drafts] [css-overflow-3] Specify extent of ink overflow (#8649)

@fantasai I refer to the issue links in the first comment, and to my comments below it. I'm not very familiar with view transitions so I don't have much to add about #8597, but I can speak to the IntersectionObserver [issue]( w3c/IntersectionObserver#295), regarding the [V2](https://github.com/w3c/IntersectionObserver/blob/v2/explainer.md) feature set. A critical aspect of that API is that it reports whether an element of interest is occluded by other content, and the occlusion detection is [based on ink overflow rectangle](https://w3c.github.io/IntersectionObserver/v2/#calculate-visibility-algo). V2 shipped in chromium in 2020, and it is [increasingly popular](https://chromestatus.com/metrics/feature/timeline/popularity/3051). One of the issues that came up in spec conversations about V2 is that it's difficult to guarantee interoperability because the extent of ink overflow is insufficiently specified.

IntersectionObserver V2 is most useful in a cross-origin embedding context, where the embedee doesn't trust the embedder to display the embedded content faithfully. In this situation, the burden falls on the embedder to ensure that the embedding page doesn't inadvertently occlude embedded content, and it's difficult for authors to do this reliably and interoperably if they can't depend on some upper bound on ink overflow rects generated by their content. For that reason, the focus of my work has been to provide a reliable *upper bound* on ink overflow, and to provide practical guidance that authors can rely on.



-- 
GitHub Notification of comment by szager-chromium
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8649#issuecomment-2008489099 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 20 March 2024 01:18:33 UTC