Adding that line (at the top of your mootools.js file) should be enough. If you want to rebuild, either wait until the mootools.net website is updated, or use github.com/kamicane/packager.
http://mootools.net/blog/2012/08/13/optimizing-mootools-builds-sans-internet-explorer/ contains all the commands you need, even though that post is written for MooTools 1.4, the packager commands are basically the same: packager register packager build Core/* On Fri, Jan 18, 2013 at 2:38 AM, hx <[email protected]> wrote: > I mean build 1.2.5 core, or can I just add the code > try { delete String.prototype.contains; } catch(e) {} to my old > mootools-core.js file ? > is it enough ? > > > 2013/1/18 hx <[email protected]> > >> howto build it ? >> >> >> 2013/1/11 Arian Stolwijk <[email protected]> >> >>> Yeah, see https://github.com/mootools/mootools-core/issues/2402 and >>> https://groups.google.com/d/msg/mootools-users/W7MHwTFHYQ4/B4HcR951XQYJ >>> >>> >>> On Thu, Jan 10, 2013 at 10:29 PM, Adriaan <[email protected]> wrote: >>> >>>> Working jsfiddle example here: http://jsfiddle.net/CfJyd/ >>>> >>>> The problem only occurs in Firefox 18 that I know of. >>>> >>>> The following html: >>>> >>>> <div class="test">Test Div</div> >>>> <div class="testIgnore">This should stay the same</div> >>>> >>>> With this js: >>>> >>>> window.addEvent('domready',function() { >>>> $$('.test').set('html','Only Test should update'); >>>> }); >>>> >>>> Results in this output: >>>> >>>> Only Test should update >>>> Only Test should update >>>> >>>> >>>> Upgrading to Mootools 1.4.5 isn't an option at the moment because of >>>> lots of plugins that use 1.2.5, can anybody point me in the right direction >>>> on getting a fix? >>>> >>> >>> >> >
