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.

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

Fixes

• #2073: Reduced redundant call to onTimeout if async option is true.
• #2083: Fixes Element.clone in IE.
• #2085: All specs are green across.
• #2110: Element.erase('class') did not clear the class.
• #2113: button.set('type', 'button') is now fixed for webkit bug.
• #2116: Fixes Element.fade chain.
• #2118: $uid method is no longer exposed

Improvements

• #2089: Added support for native mouseenter and mouseleave.
• #2134: 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.
• #2138: Native Element.fireEvent in IE is now accessible in via Element._fireEvent.

Known Issues

• Documentation fixes/additions for Element.NativeEvents, Fx, Request.JSON, and conflicts between Array and Elements methods.
• Object.each enumeration
• Possible leak with Element.adopt
• IE returns methods for some Element attributes.
• Element.Delegation problem with non-elements.

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

Get it!

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

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.

Every week the MooTools developers host an IRC OfficeDeveloper Hour where they work together to listen to your feedback, answer your questions, and develop MooTools. We do this every Tuesday at 11am EST at #mootools Freenode IRC Channel. Everyone’s welcomed to join us.

This recap includes:

• Mentions
• Answers to: Where do you guys think MooTools can improve?
• Sneak Peak to Improved Docs

• Agenda for July 19th Dev Hour

  (more…)

Every week the MooTools developers have an IRC office hour meeting where they work together to listen to your feedback, answer your questions, and develop on MooTools. We do this every Tuesday at 11am EST at #mootools Freenode IRC Channel. Everyone’s welcome so join us tomorrow.

This recap includes:

• Compare 1.3.x and Experimental 2.y.x Code Diffs

• Things to Come (Agenda’ed Office Hour, Dedicated “Hackathon” Office Hours)

  (more…)