MooTools

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 […]

More stable and well tested than ever1.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 ... [More] 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. [Less]

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 […]

More stable and well tested than ever1.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 ... [More] 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. [Less]

More stable and well tested than ever1.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 ... [More] 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. [Less]

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 ... [More] 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. [Less]

Hey folks, Just a quick survey. Reply via @mootools or leave a comment here. Are you using the Browser module? If so, why are you using it? Cheers, -Olmo

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 ... [More] 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. [Less]

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 […]

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 ... [More] 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. [Less]