- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 May 2023 13:20:22 +0000
- To: public-css-archive@w3.org
> If we do that and later want to introduce another timeline (say hover-timeline) we'll get into trouble there. While it does look a bit odd to separate between the two, they do solve quite different scenarios, so I think it won't be noticed in practice. @bramus you did tons of demos, WDYT? Would this not be relevant for any named animation timeline? If we introduce other timelines that are visible to `animation-timeline` the intention would seem to be to make them visible to other elements at which point I feel like they should participate in the same mechanism. If `hover-timeline` (or some other specific timeline) for some reason should only be usable on the same element, we could make it so that it can only be defined anonymously (e.g. similar to `scroll()` or `view()` anonymous functions) and not named. Note that no matter what we do, the JS api would allow using any element's timeline on any other element. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7759#issuecomment-1529706863 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 1 May 2023 13:20:24 UTC