- From: Bruno Stasse via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 May 2022 18:30:32 +0000
- To: public-css-archive@w3.org
If I may chime in, I hope the idea of making the timelines reachable globally has not been discarded. I have several use cases which require it. One of them is in the context of tabs implemented using scroll-snap. Tab names are displayed in a horizontal scroll container above the scroll container for the tabs. As you scroll horizontally through the tabs, the indicator moves to go below the title of the active tab. This is a very common pattern, used in Material design for instance. You might be able to hack around non-global scroll timelines by putting the tab titles container inside the tab containers, but that would complicate layout, and is not always possible. A similar use case is a navigation indicator in a fixed bar next to the title of the section currently in view in a scroll container, with the indicator moving as sections are scrolled through. The other use cases I have in mind often animate elements which use position fixed and are outside of the scroll container either because they were present in the DOM before the scroll container was added, or for z-ordering reasons. I fear limiting the access of a scroll timeline to the scroll container and what follows it in the tree would limit its usefulness and push developers to resort to twisted and inconvenient DOM manipulations. -- GitHub Notification of comment by brunostasse Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7047#issuecomment-1117670330 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 4 May 2022 18:30:33 UTC