- From: Yehonatan Daniv via GitHub <noreply@w3.org>
- Date: Tue, 05 Aug 2025 20:14:37 +0000
- To: public-css-archive@w3.org
> > What if we actually had a viewenter and viewleave DOM events which map exactly to what view() does, but without the state? (And I must say I think I'd love to have those anyway). > > A note of caution here: these proposed events might appear at first glance to be redundant with IntersectionObserver, but they are not. The biggest difference is that IntersectionObserver takes into account intermediate clipping (e.g. nested scrollers, clip-path). Of course! They also don't take transforms into account. Which is also very important. > Having said that: conceptually I think `viewenter` and `viewleave` is a helpful way to think about timeline-based triggers, whether or not they are promoted to full-fledged DOM event.s Yes. Though on second thought, I guess these are not really events that originate directly from a user interaction, so perhaps they won't really make a good fit for DOM events, perhaps more fit for an observer-style events. But the concept still stands, and I think this can help simplify things a lot. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12336#issuecomment-3156501878 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 5 August 2025 20:14:38 UTC