- From: David A via GitHub <noreply@w3.org>
- Date: Wed, 06 Aug 2025 20:43:57 +0000
- To: public-css-archive@w3.org
> One option for a syntax could be making these 2 events as functions that accept insets, or ranges, or both. Maybe even simplify them to something different (going wild here), like take a number as a threshold, kind of like `IntersectionObserver`s: > > * `viewenter(0.5)`: would be like `view()` with `entry 50% exit 50%`. > * `viewleave()`: could default to `0` which means `view()` with `cover`. > > We could also add `insets` with a separator if needed. Note the `axis` can be dropped entirely since this isn't required to compute a progress value, but rather specify a rect. Interesting idea. Would it mean that we have to support multiple triggers per animation to support any non-`once` behavior? E.g. alternate - "play on enter, reverse on exit"? -- GitHub Notification of comment by DavMila Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12336#issuecomment-3161549980 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 August 2025 20:43:58 UTC