This is a re-opening of #475
This has recently been re-discovered in the joomla-dev-general Google Group/Mailing list where a developer reported having issues with a BS-based slideshow module he developed, and thus is still a current and valid issue.
Please let mootools rest in peace!
Rest in peace? It should burn in hell!
Unhappily in this case (see the dev mailing list) someone designed a BS based slideshow module, but he was also using a componenent using Mootools for modal (BTW, don't we still use it for ToolTips?), and... crash!!
Labels |
Added:
?
|
Mootools-more and Boostrap are incompatible. End of story.
Neither libraries have attempted any sort of fix (in fact both refused to do so) so neither should we.
Just in case it can be usefull there is a UI library using MooTools based on Bootstrap: https://github.com/Behavior-UI/behavior-ui
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-07-13 08:17:24 |
Closed_By | ⇒ | smz |
...This has recently been re-discovered in the joomla-dev-general Google Group/Mailing ...
Rediscovered????? Are you kidding me ?
It's never been fixed, altough u have a fix in https://github.com/joomla/joomla-cms/issues/475
Poor and sad......
@brianteeman No one obviously cares about it anyway......
No one should be using Mootools + Bootstrap(jQuery) at the same time.
Why would Joomla want support that when both Mootools or Bootstrap projects have said it shouldn't be done??
Why would Joomla want support that when both Mootools or Bootstrap projects have said it shouldn't be done??
Because when 3.0 released Joomla was still heavily dependent on MooTools for its JavaScript API. It's less of an issue today but there are still extensions and a few core systems requiring MooTools.
Considering Joomla's already forked and hacked away at Bootstrap (without documentation, ever tried implementing event handlers on some of Bootstrap's hide events and wonder WTF it doesn't work?), at this point Joomla has accepted full responsibility for maintaining the Bootstrap JavaScript APIs because it wanted to create a MooTools and jQuery/Bootstrap friendly environment so since the project has taken it upon itself to create said fork it should resolve whatever incompatibility issues exist or whatever bugs have been introduced by creating said fork.
You can use the following code (taken from Twitter Bootstrap 2.3.2 reference code at http://getbootstrap.com/2.3.2/javascript.html#carousel): copy-paste it into an article (be sure to use editor:none and of course substitute the path to your images):
When you'll display your article you'll have your slideshow and can start it by clicking on one of the nav buttons.
Now try the same when having mootool-more loaded. You can force it by editing your index.php and put the following inside the
<head> ... </head>
section:There will be no JS errors in console, but... you will see!?