- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Nov 2023 09:52:34 +0000
- To: public-css-archive@w3.org
> How is the developer intent here different from the developer intent in `IntersectionObserver`? `IntersectionObserver` is more about reacting to an element when it's in the viewport, that's why it has options for being completely in the viewport, and everything in between. It was originally created with lazy-loading in mind. With view transitions, we're in a very visual space. So "not there" becomes more of a visual question than a layout question. If we count "partially visible" as "not there", then you'll end up with transitions where the old thing and the new thing are both visible (to some degree) in the transition, but they won't transition as part of the same group, so the user will see double. I don't think that's a desirable outcome of this feature. Also, parts of intersection observer _do_ consider ink overflow. -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8282#issuecomment-1814115155 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 16 November 2023 09:52:36 UTC