- From: Robert Flack via GitHub <noreply@w3.org>
- Date: Thu, 28 Aug 2025 17:59:07 +0000
- To: public-css-archive@w3.org
> So if I understand this correctly, unless we solve multiple timelines' enter/leave events, we have to restrict triggers to either being a single timeline trigger The reason viewenter / viewleave made this difficult is if the developer specifies different ranges, viewleave could fire without ever firing viewenter, or viewenter could fire twice without firing viewleave. The intention of having a different leave range was to only get another enter effect if you fully leave the exit area. With any of the approaches where we specify the enter and exit range on a named view timeline and then reference those events for that timeline, we can ensure that these events are paired for that timeline. If a developer chooses not to use those paired events that is fine, but at least we have made it easy to do the right thing. TLDR, we **do not have to restrict triggers** to being a single timeline trigger, but we should make it possible/easy to create enter/leave triggering events that are correctly paired. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12652#issuecomment-3234437544 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 August 2025 17:59:07 UTC