- From: Bramus! via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Mar 2023 08:38:33 +0000
- To: public-css-archive@w3.org
> So defining scroll-timeline-name in the absence of a root is an implicit root right? Correct. > 1. Handling multiple timelines attempting to attach to the same deferred timeline is complicated. Can we consider this an error? Could the cascade help here to determine the winner? Sure, it’s not the same element that’s being targeted here, but it’s the same scroll-timeline-root that’s being targeted. Totally fine with deferring this, as it would only complicate things for now. > 2. Is this intentionally only for scroll timelines? > I believe there are strong use cases for observing non-ancestor timelines for both scroll timelines and view timelines so we should have it for both. Not quite following here. How can you track an element’s position within a non-parent scroller? It’s view-timeline inside that non-parent scroller would always be inactive, no? -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7759#issuecomment-1482438410 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 March 2023 08:38:35 UTC