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
Autoscroll binds to event "onSeek". The event handler "scoll()" calls "api.next()" after a couple of seconds which in turn sends a new seek event "onSeek". Thus an intended Loop is created.
In case the user scrolls manualy the already times call to "api.next()" still is in place. Thus it may happen, that the user selects to scroll to the next element and immediately afterwards an additional scroll is performed.
Additionally every manual scroll of the scrollable creates a new event loop.
To fix this, an extended detection of times onSeek event handlers is needed. The following patch resolves the issue for us. Please revise it. It would be gread if you could add similar checks to your code.
Yep, Scrollable events are buggy (e.g. #718) and autoscroll is too buggy. Manual navigation during autoscroll makes Scrollable scrolling a bit crazy :)
Autoscroll binds to event "onSeek". The event handler "scoll()" calls "api.next()" after a couple of seconds which in turn sends a new seek event "onSeek". Thus an intended Loop is created.
In case the user scrolls manualy the already times call to "api.next()" still is in place. Thus it may happen, that the user selects to scroll to the next element and immediately afterwards an additional scroll is performed.
Additionally every manual scroll of the scrollable creates a new event loop.
To fix this, an extended detection of times onSeek event handlers is needed. The following patch resolves the issue for us. Please revise it. It would be gread if you could add similar checks to your code.
The text was updated successfully, but these errors were encountered: