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
{{ message }}
This repository has been archived by the owner on Jun 9, 2022. It is now read-only.
As well as supporting the existing JS event listener callback (scroller.addEventListener()), it'd be great if FTScroller fired standard DOM events on the scroller DOM node as well. This would enable external modules which don't have access to the scroller instance in memory - for example test suites - to listen to (and indeed, synthesise) FTScroller events on an existing node. They might need to be namespaced, as the scroll event could conflict with the native browser scroll.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As well as supporting the existing JS event listener callback (
scroller.addEventListener()
), it'd be great if FTScroller fired standard DOM events on the scroller DOM node as well. This would enable external modules which don't have access to the scroller instance in memory - for example test suites - to listen to (and indeed, synthesise) FTScroller events on an existing node. They might need to be namespaced, as thescroll
event could conflict with the native browserscroll
.The text was updated successfully, but these errors were encountered: