Articles in the ‘All’ Category

1.5.1 is out!

Written By Sérgio Crisóstomo, on Friday, August 29th 2014, 7:25am

Today we release MooTools Core and More versions 1.5.1. This continues our improvement work for both Core and More and introduces also some features that were in the queue for being added. This release fixes also a regression related to the mousewheel event.
When preparing the 1.5 release we decided that Core 1.5.x will work with More 1.5.x. This means that, inside the 1.5 space, versions should be compatible and you might be seeing Core or More releases that are not simultaneous.

In 1.5.1 we added a new dist/ folder in Core, present at the tagged commit, for those who want the Core source, as well as a needed update so you can get MooTools via Bower.

Worth a notice is also the new MooTools Packager. MooTools has always been about modularity, and for those of you that want to choose which modules to use you can now use the new MooTools Packager (for Node.js/Grunt), as well as the website builder. The new Packager allows to compile source files from the dependencies in the YAML header. You can find it on GitHub and NPM.

The main things in this release are:


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


  • Drag position calculation fix. (link)
  • Form.Validator.Extras credit card regex update. (link)
  • Fix Scroller Class to be able to use window as element. (link)
  • Added custom sort function for HtmlTable.Sort. (link)
  • Fixed Type error for empty string in Form.Validator. (link)
  • Added onLoad callback for local and cross-origin CSS assets. (link)
  • Fixed sort regex to respect sci-notated floated numbers in HtmlTable.Sort. (link)
  • Fixed scroll miss-placement while dragging and scrolling. (link)
  • Updates in Docs.

MooTools Core and More 1.5 are here!

Written By Sérgio Crisóstomo, on Monday, May 19th 2014, 4:38pm
More stable and well tested than ever

1.5 is a HUGE bug fix release with roughly 240 commits addressing new browsers that have entered the market as well as new features in the JavaScript language. The team spent a ton of time instrumenting the tests to run against Travis CI and Sauce Labs so that the source code would be easier to test. This will help to make new contributions, fixes and features to the framework and release much more rapidly.

It’s easy to underestimate the value of all the work that went into the project over the past two months.


Anyone using Core/Browser.js?

Written By Olmo Maldonado, on Thursday, February 6th 2014, 6:12pm

On our road to Version 1.5, we’re trying to eliminate some bad practices from our code. One of the things we’ve just gotten rid of, is that a few last pieces of our libraries still depended on Browser UA detection. This has all been eliminated in favour of feature detection. To help us reach a decision on where to go with the Browser module, here’s a quick survey. Reply via @mootools or leave a comment here.


MooTools on Bountysource

Written By Arian Stolwijk, on Thursday, May 30th 2013, 2:11pm

Today we enabled Bountysource for MooTools Core and MooTools More. Bountysource is a funding platform for Open Source projects like MooTools.

It works as follows: there is an issue on GitHub. You, or anyone else, can create a bounty to back the issue. Then some developer (either a MooTools Team Member or some other contributor) fixes the issue. Once it gets merged and he or she can collect the bounty!

We think this could help to prioritize issues and to increase community contributions. After all, who doesn’t like to get some pocket money to buy a beer or MooTools t-shirt!

MooTools Conference

Written By Garrick Cheung, on Thursday, April 18th 2013, 2:28pm

This year we’re thinking about getting everyone in the MooTools community together, in one place, for a weekend to meet up, chat, discuss, and have an all-around good time. That’s right, we’re trying to plan a MooTools Conference!

But before we can do that, we need your help. We’ve set up a form so we can gauge interest in a MooTools Conference. All you need to do is take a minute and answer the questions.

We’ll keep the form up until next week, but make sure you answer quickly so we can start planning this awesome Official MooTools Gathering (or OMG—which might or might not be the name of the conference).