MooTools 1.2.4Written By Aaron Newton, on Monday, October 19th 2009, 5:41pm
It’s been three months to the day since the last point release of MooTools and we’re excited about all the goodness packed into this release. At this point, the 1.2 codebase has a very stable API, and our current plan is to release these point releases every three months or so until the 2.0 codebase is online. If we find any serious bugs, though, we’ll be sure to get fixes into your hands as fast as we can.
Before we get started telling you all the yummy stuff we’ve got for you, let us first assure you that the code we released today is 100% backwards compatible with the previous versions. Upgrading should be as simple as dropping the new files in place.
MooTools Core - 1.2.4
This version of the MooTools Core is one of the most tested and refined we’ve ever released. We’ve fixed numerous small bugs, but the ones you may notice most of all are:
- Added Trident 6 (IE8) detection
- Request can take an instance of URI as a url
- JSON.stringify and JSON.parse native methods are now accessible
- DomReady always fires before load event
- Fix for creating a Request in early versions of IE6
- Fixes and optimizations for Element.getOffsets
This short list doesn’t do it justice, there have been roughly 70 commits to the core since 1.2.3, but most of these fixes are minor including adding to documentation, adding more tests, etc. The point here is that the 1.2 branch is increasingly stable, which is why we release it so infrequently.
Gecko (Firefox) Detection in 1.2.4, 1.1.2
MooTools has always used object sniffing to detect rendering engines, and while not perfect, this method has proved very reliable in recent years. However, the upcoming Firefox 3.6 marks a shift in our thinking on this subject because Gecko detection will no longer work on it without an update. We recognize the significance of this, and therefore are releasing updates for both 1.2 and 1.1 because we understand that 1.1 is still in widespread use.
MooTools More - 220.127.116.11
While MooTools Core has remained pretty much the same since the original 1.2 release, MooTools More continues to add new features that should make building sites even easier. This release is jam-packed with bug fixes and new plugins, and we’re excited to see what the community will do with them. Here’s a quick list:
- over 30 issues fixed or closed (in lighthouse)
- New feature: Element.Delegation - a partial port of event delegation from MooTools 2.0 (does not support custom events or blur/focus)
- New feature: Elements.From converts html strings to DOM elements
- New feature: Depender - a client side MooTools dependency loader ** Related: Depender App - a server side implementation (that’s much faster) - more on this in a later post
- New feature: Mask - masks elements (including the window) with a semi-opaque overlay
- New feature: Spinner - automates the creation of ajax spinners over DOM elements being updated (previously known as Waiter on Clientcide.com)
- New feature: Form.Request, Form.Request.Append - automates creating ajax forms that update HTML in DOM elements (previously Fupdate on Clientcide.com)
- New feature: HtmlTable, HtmlTable.Zebra, HtmlTable.Sort, HtmlTable.Select - interactive and auto-generated html table elements
- New feature: Keyboard - a robust event manager for keyboard groupings
- Added new option to Fx.Accordion: returnHeightToAuto
- FormValidator is now Form.Validator ** Added credit card number validator to FormValidator
- MooTools Lang is now a part of MooTools More (again)
- Added timeDiff method to Date.Extras
- Added ability to ignore scroll position with Element.Position
- Element.setPosition is now Element.position (non-breaking change)
- Added hideAll and showAll methods for OverText
- Added Element.isVisible method
- URI’s get method no longer returns null for missing parts; it returns an empty string.
- Various other tweaks and bug fixes
This release has a lot of good stuff in it, but it’s worth noting we have a LOT of other things in the oven right now.
The MooTools development team continues to grow and the more people involved with the creation of the framework, the more cool things we can release. If you want to get involved with making MooTools, all you have to do… is start writing code. Get involved on github, in the mailing list, and start getting your own plugins ready for the upcoming release of the MooTools Forge.