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.get...

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#2...

Jon Bomgardner is a contributor to the jxlib.org project. After recently joining the MooTools Developer mailing list and sharing his experience in upgrading jxlib to MooTools 1.4.2 we asked him to share his work here on the blog.What is JxLibJxLib is a JavaScript UI framework built on MooTools. It allows web developers and designers to quickly build user interfaces for their applications. JxLib is based on some sweet HMTL markup and strives to be fully CSS compliant. It is also a modular library allowing you to pick and choose from the available components as well as giving you the ability to override default behaviors and extend core classes.All of this flexibility is, in large part, du...

Those of you who follow my work over on Clientcide may already be familiar with it, but for the rest of you I wanted to write a blog posts here on MooTools.net about the work I’ve been doing on a library called Behavior - a throwback to the behavior.js library released way back in 2005 which one might consider to be philosophically an ancestor of sorts.PurposeAll well-written web sites / apps that are interactive have the same basic pattern:Each page of a site or app you build is esoteric. It may have any combination of interactive elements, some of which interact with each other (for example, a form validation controller might interact with an ajax controller to prevent it sending ...

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 exposedImprovements#2089: Added support for native mouseenter and mouseleave. #2134: Deprecates the MooTools Core Specs repository in favor of including the specs in the ...

Just a quick update to let you know we’ve added comments through Disqus to all Forge plugins.If you’re a plugin owner, you can subscribe by going to your plugin page and clicking ‘subscribe by email’ at the bottom.Remember, if you find a bug in a plugin, you should always report it in that repository’s Github Issues.As it stands, all comments will need to be moderated before they appear, just to make sure we don’t get trolled / spammed and we’re really looking forward to adding the ability to comment to the other parts of the website - particularly in documentation.Thanks to Aaron for making this happen!

Today we release MooTools Core 1.4.1 which is a small maintenance release and as such only fixes bugs that were introduced in previous releases. We have fixed the mousewheel event in Firefox, Element.fade sets the visibility CSS-property again, Event.Delegation now behaves properly if you use fireEvent and we have fixed a couple of issues with Element.setProperty and Element.removeProperty.Upgrading from 1.4.0 should not cause any backward incompatibilities. We recommend all users to update to 1.4.1 as soon as possible.Get it!Download MooTools Core 1.4.1; Build MooTools Core 1.4.1Fork / clone MooTools Core 1.4.1 from GitHub, and build it yourself with Packager.Google CDN (will be updated ...

As of today a new version of MooTools is available. This includes MooTools Core and MooTools More. We’ve communicated a lot about changes for 2.0 but we also felt we had some good stuff that would benefit you directly which we wanted to add to the 1.x releases. This good stuff contains of course numerous bugfixes but mostly one important new feature for MooTools Core: Delegation. This 1.4 release should be fully backward compatible with the 1.3 series.So all changes for 1.4.0:Move Delegation into Core.ECMAScript 5 compatibility fixes. Among them are Function.bind, Array.map and String.trimDeprecate Element.setOpacity() and Element.set('opacity'). Element.setStyle('opacity') is the o...

We at the MooTools headquarters love GitHub for all its features which makes contributing and managing our code much easier than say, five years ago. GitHub is the place to be for all cool JavaScript projects which makes following your projects of interest a lot easier. When we moved to GitHub a long time ago, the ticket system was too basic to be a real solution. Fortunately this has since improved.Especially the additions for milestones and assignees were important for us. With this in place GitHub issues can finally replace Lighthouse.The main advantages are:Everything at one place, one loginEasier to follow MooToolsSimilar to pull requestsA disadvantage is that most of the current iss...

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:MentionsAnswers to: Where do you guys think MooTools can improve?Sneak Peak to Improved DocsAgenda for July 19th Dev HourMentionsSean McArthur (seanmonstar) is working on a MooTools-based MVC Framework called Shipyard. The framework is made for working on the browser, but it can run on Node.JS. He's been testing Shipyard and we mentioned that he should try the mootools-runner which runs the specs for Core...

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 DiffsThings to Come (Agenda'ed Office Hour, Dedicated "Hackathon" Office Hours)Last week we had a small conversation of the experimental branch that Valerio has for MooTools 2.0. The conversation covered most of the comments in last week's post comments. Instead of going over them again, please take a look at last week's post.Compare 1.3.x and Experiment...

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.RecapLast week's office hour was dominated by the experimental define-2 branch by Valerio. This branch has the experimental support of Asynchronous Module Definition (AMD) and also has the proposed direction of MooTools 2.0 as mentioned in the previous blog post.From the discussion in last week's office hour, it seemed that there was confusion on the implications of adopting Valerio's 2.0 branch. In particular ther...

As suggested by our community, we're going to release a recap, or summary, of the IRC Office Hour after every session. We want to encourage you to join us on Tuesday's at 11am EST in the #mootools IRC channel, but if need be let this be your medium to discuss your perspective and your own ideas (you can also discuss in the Google Group).Topics CoveredMooTools 2.0 Community "Wish List"MooTools DocumentationFlex Box ModelRequire.JS and NamespacingMooTools RoadmapMooTools Feature: AccessorsModel Change EventsMooTools 2.0 SiteMooTools UI and MobileEvent Delegation in CoreGithub IssuesMooTools 2.0 Community "Wish List"We created a document and shared with the IRC channel a "wish list" to add r...

Last week we held our first IRC office hours in the #mootools channel on irc.freenode.net. Fifteen (15) MooTools team members were in attendance and we got a lot of responses from our community. We covered: sandboxing natives, namespacing, packaging, roadmap, MVC, and that I look like Sam from the Lord of the Rings.This is a reminder that tomorrow (June 21st) we're having another office hour and you're cordially invited to join us.Unlike last week, this week we'll have a couple of questions ready to steer the conversation. This week we'll talk about MooTools 2.0 and what you guys need to love MooTools even more. We'll be taking names down as well, for those that would like to contribute....

Starting next week, we're going to be holding regular IRC office hours for MooTools developers in the #mootools channel on irc.freenode.net. Members of the MooTools team will be on hand to answer your technical questions.We're following the footsteps of many successful office hours from other Open Source projects (Android, Mongo DB, Google App Engine, and Node.JS) because we think it's the best way to help, meet, and listen to our community.In fact, without IRC I wouldn't have become a MooTools developer in the first place. Like many of the other MooTools developers. Maybe you will too.WhenWe're going to start with a single weekly meeting on Tuesday's at 5pm - 6pm (GMT) (11am - 12pm EST)....