- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Jul 2019 22:55:50 +0000
- To: public-css-archive@w3.org
Ah, I was not familiar at all with IOv2. It seems to me that it'd miss a bunch of hard cases. It seems that IOv2 has a very concrete use-case that may not be the use-case everybody wants or needs. Also it's unclear to me if the "completely unoccluded" part of the [visibility algorithm](https://szager-chromium.github.io/IntersectionObserver/#visibility) includes the viewport or not. I assume per your description it does not include the viewport clip, right? If so I guess it does make sense to use IOv2 for some of these cases. Probably there are use-cases that still want or need a fast and sync answer for this, maybe... Also, `IntersectionObserver` only allows to observe elements, so this probably won't fly for the Shadow DOM / `display: contents` use cases that prompted the introduction of `nodesFromPoint` in #556 -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4122#issuecomment-516192696 using your GitHub account
Received on Monday, 29 July 2019 22:55:51 UTC