-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ontouchmove function throws error after content is loaded #740
Comments
When I used --- a/jquery.nicescroll.js
+++ b/jquery.nicescroll.js
@@ -1650,7 +1650,7 @@
});
self.bind(self.win, "pointerdown", self.ontouchstart);
self.bind(_doc, "pointerup", self.ontouchend);
- self.delegate(_doc, "pointermove", self.ontouchmove);
+ self.bind(_doc, "pointermove", self.ontouchmove);
} else if (cap.hasmstouch) { //IE10
self.css((self.ispage) ? $("html") : self.win, { '-ms-touch-action': 'none' });
self.css(self.rail, {
@@ -1661,7 +1661,7 @@
});
self.bind(self.win, "MSPointerDown", self.ontouchstart);
self.bind(_doc, "MSPointerUp", self.ontouchend);
- self.delegate(_doc, "MSPointerMove", self.ontouchmove);
+ self.bind(_doc, "MSPointerMove", self.ontouchmove);
self.bind(self.cursor, "MSGestureHold", function (e) {
e.preventDefault();
});
@@ -1672,7 +1672,7 @@
self.bind(self.win, "touchstart", self.ontouchstart, false, true);
self.bind(_doc, "touchend", self.ontouchend, false, true);
self.bind(_doc, "touchcancel", self.ontouchend, false, true);
- self.delegate(_doc, "touchmove", self.ontouchmove, false, true);
+ self.bind(_doc, "touchmove", self.ontouchmove, false, true);
}
if (opt.emulatetouch) { |
By the way, error also fires in IE 10 and 11 regardless device has touchscreen or not |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi all,
It seems that for laptops with integrated touch screen the following problem occurs when loading content dynamically:
Is there an override for this issue for laptops with touch-screen? maybe an option that can be disabled?
Thanks.
The text was updated successfully, but these errors were encountered: