- From: David A via GitHub <noreply@w3.org>
- Date: Tue, 01 Jul 2025 04:42:39 +0000
- To: public-css-archive@w3.org
> It isn't quite the same thing with -timeline and -range-start/end. Here, we aren't arbitrarily picking one over the other or setting one based on what the other is. One property isn't becoming wholesale invalid because another is set. The ranges are to be interpreted in the context of the timeline. `auto` means "use the document timeline", which works based on time values. We don't currently specify time ranges, but that could be a thing in the future. It's similar to `animation-timeline` and `animation-range`. > On the other hand, I guess it would still be pretty well-defined to say that `animation-trigger-event` takes precedence over `animation-trigger-timeline`. `animation-trigger` defaults to a timeline-based trigger, so if `animation-trigger-event` is present it makes sense to give it priority, I feel. I think I'm okay with keeping `animation-trigger` and its longhands as we currently have them. -- GitHub Notification of comment by DavMila Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12336#issuecomment-3021746573 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 July 2025 04:42:40 UTC