1.6.0 is out!

[Sérgio Crisóstomo]

Just to let you all know 1.6.0 is out. 

Available in the website and at Google's CDN (https://developers.google.com/speed/libraries/#mootools)

http://mootools.net/blog

There is a open issue about new communication channels, feedback is welcome :)

https://github.com/mootools/mootools-core/issues/2763

Cheers!

[Bryan Garaventa]

Excellent, have any of the prior API method names changed from that to this one?

 

I’m going to need to plug this into the accessible widget archive for MooTools at

http://whatsock.com/bootstrap/mootools/

and

http://whatsock.com/mootools/

 

It’s just a matter of swapping one file out for the new, but it would help to know if there are any conflicts.

 

Thanks,

Bryan

--

---
You received this message because you are subscribed to the Google Groups "MooTools Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mootools-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sérgio Crisóstomo]

Hi Bryan,

I don't know whatsock in depth so I cannot answer with confidence.

In the compat layer we made no API changes.
In the no-compat layer we made a change to adapt to ES6 "Array.from". 

We renamed the ".from" method in Array, Function, String and Number to ".convert".

Cheers

[Bryan Garaventa]

Thanks J

 

That shouldn’t cause any problems, the widget modules primarily tap into the rendering and AJAX methods, so if these are the same even nocompat should be fine. I’ll give it a swing later and see what happens.

 

All the best,

Bryan

 

From: mootool...@googlegroups.com [mailto:mootool...@googlegroups.com] On Behalf Of Sérgio Crisóstomo

Sent: Thursday, January 21, 2016 12:49 PM
To: MooTools Users <mootool...@googlegroups.com>

--

[Bryan Garaventa]

Hi,

I think I found a bug in MooTools, but it’s hard for me to tell.

 

It seems that this occurs in the earlier version of MooTools too, as well as the latest version, which can be seen in Chrome at

http://whatsock.com/bootstrap/mootools/

 

If you activate the Carousel tab, MooTools appears to be choking on the line "testNode.style is undefined" within MooTools Core. It also won’t render at all in Firefox, which is strange, but it does in IE11.

 

Any idea what would be causing this?

 

You can see the MooTools version file and code file in the GitHub repo at

https://github.com/accdc/bootstrap-mootools

 

Within the folder js/mootools-core.js.

 

It would be great to track down why this is occurring.

 

Best wishes,

Bryan

 

 

From: mootool...@googlegroups.com [mailto:mootool...@googlegroups.com] On Behalf Of Sérgio Crisóstomo

Sent: Thursday, January 21, 2016 12:49 PM
To: MooTools Users <mootool...@googlegroups.com>

Subject: Re: [Moo] 1.6.0 is out!

--

[Bryan Garaventa]

Hi, as a quick update, I believe I’ve traced this to the syntax of a Request instance that pulls in XML content, which is failing for some reason.

 

Do you have documentation for the correct syntax for parsing XML content using a Request object?

 

Thanks,