It looks like something in canvas is using the $ function instead of jQuery(). According to this StackOverflow post you can do conflict resolution from MooTools in a similar way that you can for jQuery.
After scouring the net, it seems *unbelievably* mootools 1.3 implements a new Type variable too, so gets in the way of MS Ajax stuff big time! This is really something that would be easilly avoided by the mootools crew, but this is how it is. For someone interested: https://mootools.lighthouseapp.com/projects/2706/tickets/1045-asp-net-bug
.
I have to check if this happens with 1.2.4, and if my code runs on that...
jquery, $ and mootools conflicts
When using canvas editing jquery gets hold of $ and ruins mootools code in page.
I can see jquery.noconflict-invoke.js loaded. But still $ is jquery's and not mootools'.
Outside a canvas session, the page works fine, and there are no conflicts.
Thanks,
Duarte
It looks like something in canvas is using the $ function instead of jQuery(). According to this StackOverflow post you can do conflict resolution from MooTools in a similar way that you can for jQuery.
Sebaastian,
After scouring the net, it seems *unbelievably* mootools 1.3 implements a new Type variable too, so gets in the way of MS Ajax stuff big time! This is really something that would be easilly avoided by the mootools crew, but this is how it is. For someone interested: https://mootools.lighthouseapp.com/projects/2706/tickets/1045-asp-net-bug
.
I have to check if this happens with 1.2.4, and if my code runs on that...
Duarte
So to close this thread. Mootools 1.2.x does work. It is 1.3.x that introduced a new Type variable.
Duarte
is working on a reply...