- From: David A via GitHub <noreply@w3.org>
- Date: Mon, 30 Jun 2025 13:13:32 +0000
- To: public-css-archive@w3.org
> Yes, it's not optimal, but you can see we already have a syntax like `auto | [ <timeline> <ranges> ]`, so ranges are not allowed with `auto`. So if both are specified this becomes invalid at parse-time. Same with my suggestion above that includes `event(<dashed-ident>)`. > 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`. > > The thing we need to acknowledge here is that **triggers are not directly associated with elements**. And IMO making their declaration a separate property is not a good design. Of course, if we just take the trivial case of declaring timelines with `scroll()`/`view()` then we sort of try to avoid that issue, but like your example above, if an author defines the timeline on one element and references it on the trigger, then the trigger declaration becomes an annoyance. > I gave that example just as a weird case that would be possible but may not really be useful to authors - I don't think it in any way represents this API format getting in an author's way as they wouldn't *need* to use a dashed ident. -- GitHub Notification of comment by DavMila Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12336#issuecomment-3019109321 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 30 June 2025 13:13:33 UTC