- From: webdevelopers-eu via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Aug 2024 06:15:55 +0000
- To: public-css-archive@w3.org
Unlike TabAtkins' opinion in the IRC chat, I strongly support the idea of implementing Promise rejection if a scroll is interrupted. As I mentioned in #3744 , the intended effect of `scrollIntoView` is to bring the specified element into view. If this does not happen for any reason, the promise should be rejected, as the action was not fulfilled. There are specific scenarios where this should occur, such as: * The element is removed or stops being rendered before it reaches the visible part of the viewport. * The smooth, time-dependent scrolling is interrupted programmatically or by user action. Simply put, the goal of `scrollIntoView` is to bring an element into view. If this is achieved, the promise should be fulfilled; if not, the promise should be rejected. This aligns with the natural and expected behavior that any programmer would anticipate when triggering an action intended to produce a specific result. -- GitHub Notification of comment by webdevelopers-eu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1562#issuecomment-2295748204 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 19 August 2024 06:15:56 UTC