- From: Bramus! via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Sep 2022 13:22:29 +0000
- To: public-css-archive@w3.org
bramus has just created a new issue for https://github.com/w3c/csswg-drafts: == [scroll-animations-1] currentTime when scroll range is 0 (again) == In https://github.com/w3c/csswg-drafts/issues/7401 we resolved on making the timeline inactive in the absence of a scroll range. Playing around with the implementation in Chrome Canary _(with Experimental Web Platform Features flag)_, I’m starting to doubt this resolution. - In https://codepen.io/bramus/pen/KKoGNye?editors=1010 it shows a progress bar at the top. As you scroll down, the progress bar grows from 0% width to 100%. - https://codepen.io/bramus/pen/YzLxJZe/f0eefc95ba1d631d2dc081ea60ac9f0b is a fork from the demo above. Only difference is that it uses short content. As there is no scroll to happen, the progress bar remains at 0% even though you are at “the end of the content”. From a UX perspective, one could argue if there’s a need to show a full progress bar in the second case or not. However, I can imagine other situations – e.g. where something fades in as you scroll down – that would need to be visible in case of no scroll range. Maybe we should revisit? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7778 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 22 September 2022 13:22:31 UTC