- From: Yehonatan Daniv via GitHub <noreply@w3.org>
- Date: Tue, 19 Aug 2025 14:46:11 +0000
- To: public-css-archive@w3.org
> > I'm worried that while we overlooked the fact that timelines are one-dimensional, which we managed to ignore so far since webpages are rarely scrolled in 2D, this won't be so easy to overlook with pointer timelines. I.e. trigger if your pointer crosses a point in Y axis, but is not really on top of an element on the X axis. > > Yes, I had considered this as well. If we pursue view-trigger-* instead of timeline-trigger-* then we could constraints in both axes. OK, this may be an option if we really want to split view-based triggering and other events. I'm not sure how much of control we want to allow there, because this already expands to 4(!) ranges - something that the events I suggested try to avoid. I also worry we may get some pushback, design-wise, about adding another specific property just for `view-trigger` and have all the rest of the events as values for `event-trigger`? -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12336#issuecomment-3201065698 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 August 2025 14:46:12 UTC