MooTools

Today we release MooTools Core 1.4.4 which is a critical maintenance release. 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). See this issue for a full explanation and solution.

We recommend that all users upgrade to 1.4.4 as soon as possible.

Fixes

• #2160: Fx.Tween/Fx.Morph problem with ‘%’ unit
• #2175: IE Leak: Array.flatten
• #2178: IE doesn’t set value when creating element if css attributes are used
• #2241: Slick.finder index selector
• #2247: Element.get not reading custom attributes in IE7/8
• #2248: contains causes “Out of Stack Space” in IE
• #2252: Element.getParents doc clarification
• #2262: SVGAnimatedString causes Slick error
• #2266: Calling setOpacity with null does not remove the style
• #2275: Update Slick to 1.1.7

Known Issues

• #2184: IE9 on Windows Server throws exception; can’t continue
• #2194: Function#bind ES5 bug when bound function is called as part of a new expression
• #2199: Browser.version always returns the same for Android 2-4
• #2207: Fx.cancel() should clear animation so Fx.resume() will not continue it
• #2214: IE8 - Cannot inject into window.opener
• #2225: IE in-page memory leak when using removeChild
• #2236: IE8 tween/morph clip:rect breaks
• #2243: Memory leak with request class
• #2245: Element.getOffsets() is broken in iOS 4.3 if using -webkit-transform
• #2265: new Element(‘style’, {text: ”}) throws IE exception
• … and more

These issues will be fixed subsequently prior to release of the next maintenance release, 1.4.5.

Contribute

These fixes and improvements would not have happened if you didn’t submit an issue (ticket) to the MooTools Core Issues, or reporting your problems in the MooTools User Group. Send us your (MooTools) issues (or feature requests) so that your favorite JavaScript framework keeps getting better.

Get it!

• Download MooTools Core 1.4.4; Build MooTools Core 1.4.4
• Fork / clone MooTools Core 1.4.4 from GitHub, and build it yourself with Packager.
• Google CDN (will be updated soon)
• Browse the Documentation for Core & More.

Today we release MooTools Core 1.4.3 which is a small maintenance release. Upgrading from 1.4.2 should not cause any backward incompatibilities. We recommend that all users upgrade to 1.4.3 as soon as possible.

Fixes

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

Known Issues

• #2129: < IE9 sets width/height attribute once, and doesn’t update on other loads
• #2130: Object.each doesn’t address IE DontEnum bugs like Object.extend and others
• #2160: Fx.Tween/Fx.Morph problem with ‘%’ unit
• #2168: Fixes 2129.
• #2175: IE Leak: Array.flatten
• #2178: IE doesn’t set value when creating element if css attributes are used
• #2183: Incorrect event.key from some keypress events in Firefox
• #2184: IE9 on Windows Server throws exception; can’t continue
• #2185: Fix #2184: IE9 on Windows Server throws exception; can’t continue
• #2188: Fixes #2178 - A input field should keep its value even when the type property is changed (in IE)
• #2189: Uncaught TypeError: Property ‘id’ of object # is not a function
• #2193: Element clone storage again
• #2194: Function#bind ES5 bug when bound function is called as part of a new expression
• #2196: it’s better for getStyle method always returns style value with px unit
• #2199: Browser.version always returns the same for Android 2-4
• … and more

These issues will be fixed subsequently prior to release of the next maintenance release, 1.4.4.

Contribute

These fixes and improvements would not have happened if you didn’t submit an issue (ticket) to the MooTools Core Issues, or reporting your problems in the MooTools User Group. Send us your (MooTools) issues (or feature requests) so that your favorite JavaScript framework keeps getting better.

Get it!

• Download MooTools Core 1.4.3; Build MooTools Core 1.4.3
• Fork / clone MooTools Core 1.4.3 from GitHub, and build it yourself with Packager.
• Google CDN (will be updated soon)
• Browse the Documentation for Core & More.

The MooTools team is very happy to announce a simultaneous update of both Core and More repositories. The past year was amazing for us. We had a great hackathon in London, we gave you MooTools 1.3, added a lot of new people to our team and improved everything around the code. The results of the MooTools survey clearly showed that we are doing the right things and we intend to make MooTools even better in 2011. We spent the past weeks fixing bugs and adding new features on both projects. This is what’s new:

Changes

• Lots (and by that I mean LOTS) of documentation improvements, clarifications and cleanups
• Updated Slick to 1.1.5 and improved the speed of our Slick selector engine
• Added delegation support for submit, focus, blur, reset, change and select events in MooTools More
• If available the native JSON methods are now used in JSON.decode and JSON.encode
• Multiple Pseudos click:relay(a):once (demo)
• Two new pseudo events: :throttle and :pause
• Added String.truncate to String.Extras in More
• More than two hundred changes to increase the stability of both Core & More

I am also pleased to announce our newest addition to the MooTools More team, Jacob Thornton, who is a great developer, currently working for Twitter. He has put a substantial amount of work into making MooTools More even better.

Be sure to check out the updated demos in our new demos section.

Get it!

• Download MooTools Core 1.3.1; Build MooTools Core 1.3.1
• Build MooTools More 1.3.1.1
• Fork / clone MooTools 1.3.1 from GitHub, and build it yourself with Packager.
• Read the commit logs to see precisely what has changed.
• Browse the Documentation for Core & More.
• Please report any bugs you can find on Lighthouse, our bug tracker.

We hereby announce the immediate availability of MooTools More 1.3.0.1. We have updated all of MooTools More’s code to work with the recently released Core 1.3 without 1.2 compatibility. Besides the API update, 1.3 improves stability and introduces some awesome new features.

Awesome new features? What awesome new features?

(more…)

Good news, everyone! We are extremely happy to announce the official release of MooTools Core 1.3 after almost a year of development. You might call us perfectionists, but we’re now ready to call the 1.3 release complete and stable. For those of you who have been waiting to make the switch, now would be the perfect time. In addition, MooTools Core 1.3 is fully backwards compatible with all documented functionality of MooTools Core 1.2, but more on that later.

(more…)