MooTools

At one point a few years back, most developers considered MooTools to be the best JavaScript framework around, and even expected it to beat jQuery and become the World's most used JS technology.

But things didn't pan out as expected and jQuery is currently used on over 50% of all sites on the Internet, while MooTools development is mostly dormant and scarce.

This is due to MooTools complexity, a framework that requires a high-degree of both JavaScript knowledge and OOP coding.

Regardless of this fact, the framework has still garnered lots of attention and plenty of followers, developers that have contributed to its code and with plugins.

MooTools currently is split up into multiple modules, which programmers can add or remove to the framework's core whenever needed.

Lots of features are supported with MooTools, all very well-documented, either on its homepage, or via the vast number of programming tutorial sites on the Internet.

Some of the apps and websites that use or have used MooTools in the past include Bing, Joomla, Vimeo and many other more.

What is new in this release:

• Rename .from method in Array, Function, String and Number
• New feature: Class.Thenable
• Add Safari 9 to Sauce Labs tested browsers
• Added ESLint to Grunt specs to keep code styled and clean
• Gruntfile refactor
• MooTools specs goes Mocha
• Specs upgrade, refactor and cleanup
• Fix so the legacy $pick gets exported to global
• Fix so Event Class gets exported to global

What is new in version 1.5.1:

• Mousewheel regression fix for Chrome and Firefox.
• DOMEvent's wheel property now listens for DOM3 wheel event also.
• IE8 iFrame leak fix.
• Added postMessage to NativeEvents.
• Fixed setter so IE7/8 can set text of style element.
• Normalize values on newElement for radio and checkbox types.
• Fixed svg element size.
• Fixed getter behavior for border-radius.
• Added fix for IE8 to be able to set HTML into style element.
• Added option to trigger xhr.withCredentials without HTTP auth.
• Added the PATCH and HEAD methods to Request.
• Fixed hasClass without classList to comply with ES6.
• Added fix for IE9 when setting an input type to "email".
• Fix for IE when removing delegated "submit" event from destroyed element.

What is new in version 1.5:

• Swiff is gone from Core (now found in More)
• Many of the user agent properties on Browser are now deprecated and MooTools depends on feature detection instead
• Added support for IE11 so that Browser.ie continues to work, but is undefined in compatibility mode. See this pull request for additional information
• A tremendous amount of work done to overhaul the unit tests, the test runner and integration with Travis CI and SauceLabs. This new test suite can also run locally, opening and testing local browsers
• Speed improvements for managing Element classes (using the new classList API available in modern browsers)
• appendHTML method added to Element
• Fx.isPaused() method added to Fx
• String.contains is now implemented according to the new ES6 standard
• getComputedStyle is now the default engine behind the getStyle() method
• Build system now uses Grunt
• Spinner now has WAI-ARIA support
• Form Validator now uses event delegation to watch inputs and whatnot
• New Array.Extras method: Array.pluck
• New Event move in Slider.js
• Numerous updates to language files
• Swiff moved to More, from Core
• Added support for :keys(+) in Element.Event.Pseudos.Keys
• Dependency on Core's now deprecated Browser flags removed

What is new in version 1.4.5:

• 1.4.5 brings a critical bugfix for Fx.CSS which caused many troubles for tweening and morphing your element styles.

What is new in version 1.4.4:

• 1.4.3 release introduced a bug as a result of fixing another bug. Specifically, 1.4.3 did not allow custom attributes (e.g. data- or non-standard attributes). This and others have been fixed.

What is new in version 1.4.3:

• IE7/8 getProperty returns functions
• Documentation: Request.JSON's behaviour of onFailure
• Document conflicts between Array and Elements methods
• Missing Fx.options.frameSkip documentation.
• Re-add undocumented from argument to Element.fade
• Element.js memory leaks
• Added Element.NativeEvents to docs
• Added Fx.isPaused() method
• Packaging issue fix. Build header and Core.js yml header collide
• Added special note to Element.empty
• IE7 Crash with Mootools Core 1.4.2
• Cannot set numerical 0 values to form fields.
• Array#filter should store this[i] in a variable before calling the callback.
• Fixed propertychange on an input[type=radio] with this.checked fires standard onChange
• UID remnant which prevented proper cleaning of elements and their storage
• element.erase( ‘html' ) sets content to text ‘undefined'

What is new in version 1.4.2:

• Added support for native mouseenter and mouseleave.
• Deprecates the MooTools Core Specs repository in favor of including the specs in the Core repo. Due to ease of development.
• Series of new specs and refactoring of old specs. Specs are all passing and much faster.
• Native Element.fireEvent in IE is now accessible in via Element._fireEvent.

What is new in version 1.4.1:

• Fixed:
• mousewheel event in Firefox
• Element.fade sets the visibility CSS-property again
• Event.Delegation now behaves properly if you use fireEvent
• A couple of issues with Element.setProperty and Element.removeProperty.

What is new in version 1.4.0:

• Move Delegation into Core.
• ECMAScript 5 compatibility fixes. Among them are Function.bind, Array.map and String.trim
• Deprecate Element.setOpacity() and Element.set('opacity'). Element.setStyle('opacity') is the only correct way now (the same applies for getters).
• Disable the 1.2 compat layer by default in the builder.
• Revamp Element.getProperty, Element.setProperty. Element.getProperty uses Slick.getAttribute now to share this code and save some bytes.
• IE7 doesn't crash anymore when cloning an element twice.
• The Selectors documentation is back and updated for Slick.
• Update Slick to 1.1.6
• Unified change event behavior across browsers.
• Renamed Event to DOMEvent so it will not conflict with the native Event object.

What is new in version 1.3.2:

• Fixed Slick bug with ~div-like selectors
• Fixed MooTools in the Node.js environment
• Fixed an exception in DOMReady in Chrome when the page with MooTools was in an IFrame
• Fixed setOpacity for very small numbers in IE
• Fixed an exception in FireFox 4 when MooTools tried to overwrite document.head
• Added the possibility to create elements with boolean values with an selector, e.g. new Element('input[checked]');

Requirements:

• JavaScript enabled on client side