MooTools 1.1.2

[Aaron Newton]

Greetings Joomla People,

My name is Aaron. I work on MooTools.

Today we released MooTools 1.2.4 and 1.1.2 (http://mootools.net/blog/
2009/10/19/mootools-1-2-4/). I know you are all working hard on the
next version of Joomla and already have our 1.2 code base included,
but I wanted to reach out to you about our 1.1.2 release,
specifically, this bit (from the blog post):

~~~~~~~~~~~~~~~
MooTools has always used object sniffing to detect rendering engines,
and while not perfect, this method has proved very reliable in recent
years. However, the upcoming Firefox 3.6 marks a shift in our thinking
on this subject because Gecko detection will no longer work on it
without an update. We recognize the significance of this, and
therefore are releasing updates for both 1.2 and 1.1 because we
understand that 1.1 is still in widespread use.

Looking towards 2.0, we have overhauled our browser detection to be
based on the user agent string. We realize that this is not without
its forward compatibility risks, however it is the standard practice
among JavaScript libraries because of potential issues as Firefox 3.6
demonstrates. As browsers grow closer together, looking at “features”
to separate them will become more difficult and risky. User agent
strings, on the other hand, have remained very consistent in recent
years with the exceptions being in mobile browsers and with Google
Chrome coming on stage. With 2.0, browser detection will only be used
where it would be impossible not to, in order to give the consistent
experience across browsers that one would expect from a world-class
JavaScript framework.

For those of you still running 1.1, it is imperative that you update
to 1.1.2. When we get 1.1.2 up on Google’s JavaScript CDN service,
those of you requesting 1.0 or 1.1 from that service should see the
upgrade without doing anything. If you do not update your 1.1 scripts,
users visiting in Firefox 3.6 and beyond will likely encounter issues.
~~~~~~~~~~~~~~~

The nutshell is that we were using feature detection to determine if
the user was in Firefox (Gecko), and the Mozilla team removed the
feature. What we want to know is, how can we help your community avoid
these issues. We're at your disposal if you need us to do anything.

Best,
Aaron Newton

[Ian MacLennan]

Thanks Aaron,

Is the update from 1.1.1 to 1.1.2 isolated to this one issue?  Or have other things been rolled into the release as well?  Is there anything in particular we should be looking at when doing regression testing?  We're hoping to release a new version of our 1.5 branch to tidy up some issues so it is probably as good a time as any to get this one in.

Ian

[KenMcD]

Aaron,
Where are the v1.1.2 file downloads?
The downloads page only has v1.2.4.
And the only other files I could find are in github.
Where are the 1.1.2 drop-in replacement files available for download?
Thanks.

[Djamil Legato]

Hello,

I've set up a page for downloading MooTools 1.1.2 with a bit of
technical clarifications to this issue too. It is temporary placed at
my space: http://mootools112.djamil.it/ (the files are pointing to the
official mootools.net side).

To clarify this update:
Nothing but the Gecko check has been changed in MooTools 1.1.2,
everything is going to work exactly the same as in 1.11.
If you could push this update in before your next release, that would
be nice.

Thanks and sorry for the delay.

- Djamil Legato / MooTools Core Developer

[Aaron Newton]

Sorry, my email on this group is set to digest and I forgot to monitor
this thread more closely. I'll reply to all the comments here now.

> Is the update from 1.1.1 to 1.1.2 isolated to this one issue?  Or have other
> things been rolled into the release as well?  Is there anything in
> particular we should be looking at when doing regression testing?  We're
> hoping to release a new version of our 1.5 branch to tidy up some issues so
> it is probably as good a time as any to get this one in.

The ONLY thing in this release is the browser issue for gecko. Here
are the only two lines changed:

//in Core.js
var MooTools = {
- version: '1.11'
+ version: '1.12'
};

....

-else if (document.getBoxObjectFor != null) window.gecko = true;
+else if (document.getBoxObjectFor != null || window.mozInnerScreenX !
= null) window.gecko = true;

>
> Ian
>
>
>
> On Mon, Oct 19, 2009 at 7:27 PM, Aaron Newton <anut...@gmail.com> wrote:
>
> > Greetings Joomla People,
>
> > My name is Aaron. I work on MooTools.
>
> > Today we released MooTools 1.2.4 and 1.1.2 (http://mootools.net/blog/

> > 2009/10/19/mootools-1-2-4/<http://mootools.net/blog/%0A2009/10/19/mootools-1-2-4/>).

[Aaron Newton]

this is what I get for not reading all the way through the thread;
Djamil is ahead of me as usual.

On 20 Oct, 22:55, Djamil Legato <w00f...@gmail.com> wrote:
> Hello,
>
> I've set up a page for downloading MooTools 1.1.2 with a bit of
> technical clarifications to this issue too. It is temporary placed at

> my space:http://mootools112.djamil.it/(the files are pointing to the

[ssnobben]

There is some conflicts for many people with IE7 IE8 for Joomla and
Mootols as discussed here [IE7 fatal error] Jtooltips - window.addEvent
('domready'

http://forum.joomla.org/viewtopic.php?p=1361496&sid=7c796a89b7f1a62ee22b4ec3977d8f74#p1361496

Hope this is fixed and also for J 1.5.15 ?

rgds

[infograf768]

Best is to create an artifact and give all details on testing
procedure with default Joomla installation.

On 23 Oct, 10:52, ssnobben <ssnob...@hotmail.com> wrote:
> There is some conflicts for many people with IE7 IE8 for Joomla and
> Mootols as discussed here [IE7 fatal error] Jtooltips - window.addEvent
> ('domready'
>

> http://forum.joomla.org/viewtopic.php?p=1361496&sid=7c796a89b7f1a62ee...