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
Mootools more conflict #10
Comments
Thanks. This isn't a case I will be supporting personally. I can't see a good reason for including both jQuery and MooTools on a page. But I'll leave this issue open here for a bit in case anyone else wants to investigate and find out what the issue is. |
I totally disagree. No one wants to add multiple javascript libraries to his site but there are cases that this just happens ( a CMS for example ). That's why the no-conflict mode is implemented by jQuery. Anyway i don't know if the issue is coming from Mootools or your plugin. |
Right. Which is why I said good reason - I can't see a good reason to use a dodgy CMS, either. But I know this kind of thing is unavoidable sometimes. I don't know the cause either, which is why I'll leave this open for a while to see if anyone has any suggestions. Cheers for reporting :) |
Closing as won't support. |
Hi. There is an issue when using your move event plugin in a page with Mootools more loaded. The following steps can reproduce the issue:
Note that since you use the move plugin to the swipe plugin this issue also occurs in the swipe plugin.
The text was updated successfully, but these errors were encountered: