Comments on: MooTools 1.2.3 Released

By: Justin Clean

Justin Clean — Fri, 10 Sep 2010 18:42:57 +0000

Great job with the release, cant wait to see the updates! Thank you again for all your hard work and effort with the release.

By: Jack Heater

Jack Heater — Mon, 30 Aug 2010 23:54:18 +0000

Anuj, try switching up the variables to see if you get any results.

By: Anuj

Anuj — Wed, 19 Aug 2009 06:45:35 +0000

Hi All,

Please help me. When I have to replace $(), I will use document.id() but when I want to replace $$() what will I use?

By: BMo

BMo — Fri, 31 Jul 2009 10:59:52 +0000

What do you changed on submiting form-elements?

My function, don't send any submit buttons anymore, but I need the name and the value of the submit-Buttons in the form.

html_element.addEvent('submit', function(e) { e.stop(); this.set('send', { method: 'post', onComplete: function(response) { general_function_destroyLoadingAnimation(zielDiv); zielDiv.empty().set('html', response); //domready ausführen if(pageLoadManager!=null){ pageLoadManager.initialize(); }else{ pageLoadManager = new PageLoadManager(); } } }); this.send(); });

By: Malih

Malih — Fri, 10 Jul 2009 12:30:27 +0000

I wonder whether mootools 2.0 will make available feature like the new Web worker threads in FF 3.5 to Internet Explorer, or any other browser that doesn’t support them for that matter.

By: razvansg

razvansg — Tue, 30 Jun 2009 14:27:44 +0000

When exactly are you guys planning to release Mootools 2.0? I read that it will be this summer. Like july or august or something?

And what exactly will be new in 2.0? A little info please! :)

Thank you for your great work.

By: Ollie Maitland

Ollie Maitland — Fri, 26 Jun 2009 08:29:00 +0000

Excellent release, keenly awaiting MooTools 2

By: Brade

Brade — Wed, 24 Jun 2009 20:34:40 +0000

To elaborate on my last comment: the new mootools does something (not sure what) that does NOT play nice with IE’s “protected mode” — we test our sites on IE using its default settings, since most users won’t ever change them. by default “protected mode” is on and renders a blank page if something triggers it. Also I found it doesn’t re-trigger by hitting reload. You have to enter the page via a link each time you want to test. And I ultimately found that by commenting out the line that includes mootools, my page showed up. when I uncommented, the page goes blank and has the two javascript errors I mentioned earlier. Just an FYI for the devs, hopefully it’s a quick fix…

By: Brade

Brade — Wed, 24 Jun 2009 18:59:00 +0000

Just curious if anyone else has had issues with the compressed version of mootools causing sites in IE to blank out? I got a couple of javascript errors when I loaded my site in IE (but not firefox) and both errors were from the mootools core JS file…

By: Ben

Ben — Tue, 23 Jun 2009 18:02:02 +0000

Could we pleeease get someone to fix the Google Search on the docs on this site? It flat out does not work correctly. It’s useless as it is. Thanks. :-)

By: Savage

Savage — Tue, 23 Jun 2009 07:24:26 +0000

Any compatibility feature for IE 8? Or was it already supported with no bugs in 1.2.2?

By: asvanu

asvanu — Mon, 22 Jun 2009 21:05:54 +0000

Thanks for the update :)

By: БОШ

БОШ — Mon, 22 Jun 2009 17:06:26 +0000

Good news! Thanks a lot!

By: Htbaa

Htbaa — Mon, 22 Jun 2009 14:58:57 +0000

Thanks for the update! Great to hear that 2.0 will be 100% compatible. Keep up the good work!

By: Botanicus

Botanicus — Mon, 22 Jun 2009 10:05:29 +0000

Why is $() defined just when another framework isn’t found? I haven’t seen corresponding commits, so please correct me if I’m wrong, but I think it’s much better to define $() in all cases and let user decide which framework load first (this will not have $() defined because the second one rewrite it). Am I right? If not please explain.