You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[X ] Feature request
[ ] Documentation issue or request
Current behavior
Scrollable elements scroll only in one direction. Also, the animation cannot be stopped programmatically. Finally, animation continues even after scroll has been completed (when providing a large duration value).
Expected behavior
Given target1 and target2, the ability to scroll from target1 to target2, which would imply scrolling up when target2 is below target1 and scrolling down when target2 is above target1.
Also, ability to programmatically stop animation prior to the execution defined by "duration" finishing.
Finally, the animation should stop (and raise and event) when scrolling is completed, not when duration (time) runs out (assuming that scrolling will always complete in the time passed as duration).
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
We have screens with lots of data that we would like to "auto" scroll from top to bottom, to be followed by either a scroll up from bottom to top, or by jumping back to the top, and start scrolling down again.
Environment
Angular version: 14
Your version of `@nicky-lenaers/ngx-scroll-to`:
14.0.0
Browser:
- [X] Chrome (desktop) version XX
- [X] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: 18.10.0
- Platform: Windows, Android
Others:
The text was updated successfully, but these errors were encountered:
I'm submitting a...
Current behavior
Scrollable elements scroll only in one direction. Also, the animation cannot be stopped programmatically. Finally, animation continues even after scroll has been completed (when providing a large duration value).
Expected behavior
Given target1 and target2, the ability to scroll from target1 to target2, which would imply scrolling up when target2 is below target1 and scrolling down when target2 is above target1.
Also, ability to programmatically stop animation prior to the execution defined by "duration" finishing.
Finally, the animation should stop (and raise and event) when scrolling is completed, not when duration (time) runs out (assuming that scrolling will always complete in the time passed as duration).
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
We have screens with lots of data that we would like to "auto" scroll from top to bottom, to be followed by either a scroll up from bottom to top, or by jumping back to the top, and start scrolling down again.
Environment
The text was updated successfully, but these errors were encountered: