- From: Robert Flack via GitHub <noreply@w3.org>
- Date: Tue, 23 Sep 2025 18:30:02 +0000
- To: public-css-archive@w3.org
> My question is: do the uninterrupted scrollers still continue their scrolling even after one got interrupted? This is about the observed behavior and not about the returned promise. To explain in a different way, suppose a ScrollIntoView call starts smooth scrolling in scrollers `A`, `B` and `C`, and then a `B.scrollBy(0)` call interrupts the smooth scrolling of `B`. Shouldn't `A` and `C` immediately stop scrolling? This is getting beyond the issue of when the promises should be resolved. Whether or not any of the ongoing scrolls is interrupted, the scrollIntoView call should resolve when all of the dependent scrolls' promises have resolved. If they are interrupted, then the overall promise may resolve sooner. We can separately debate how interrupting a scroll should affect ongoing scrolls but I don't see what that has to do with the promise resolution. That said, this is a simple thing to test, I put together a test case https://codepen.io/flackr/pen/pvgJQxP . Chrome and Safari only interrupt the scroll of B, Firefox stops the scroll of B and C. I think that it doesn't make sense to stop scrolling A since you would still be able to scroll to the position that brings the B scroller into view. Stopping scrolling C (as firefox does) might make sense since it's no longer necessarily going to come into view. Though I could also see an argument for continuing it. Either way, this seems like a completely separate issue. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/12355#issuecomment-3325113440 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 September 2025 18:30:03 UTC