All scripts require MooTools 1.2.x unless otherwise stated.

MooTools 1.3 Available

Posted by Matt on Nov. 7, 2010 at 14:00

Well, for a while now MooTools 1.3 has been out. Some of the new feature are quite nice.

I havn't gone looking to far into it yet I must admit however, favourite feature is

new Element('div#my_id.my_class')

A little quicker to type that

new Element('div', {
    'id': 'my_id',
    'class': 'my_class'
});

The other thing I can imagine would be useful for some are the updates to the Browser class. It seems there are now properties for each major browser version so you can now use Browser.ie6 rather than Browser.Engine.trident combined with Browser.Engine.version.

A snippet of features from the MooTools Blog

  • Revised Core.js, added even more abstractions
  • Fixes for a lot of element attributes (maxlength, etc…)
  • New feature tests further minimize reliance on browser detection
  • New Browser.js for the rare times when feature detection doesn’t cut it
  • New DOMReady implementation improves speed and fixes edge case bugs
  • Array.each now chains! Yes, indeed.
  • Support for touch events on breakthrough communication devices
  • Array: forEach, map, some, every and filter now behave according to the ES5 Spec in IE (skipping undefined values)
  • IE opacity style fixes
  • If you build without 1.2 compatibility, Hash is gone. MooTools More 1.3 will provide Hash from now on.
  • Elements is now an array-like-object instead of a real array.
  • Additions to Request — authentication, onprogress and other cool stuff
  • Numerous stability improvements
  • … and more!

Although there are changes from 1.2, everything is still available, however there is a lot which has been deprecated so, where possible, get re-writing (not right away) if you want to continue to just upgrade in future.