[Moo] firefox 3.6 and mootools 1.1.2 / 1.2.4.2

3 messages Options
Embed this post
Permalink
Dimitar Christoff

[Moo] firefox 3.6 and mootools 1.1.2 / 1.2.4.2

Reply Threaded More More options
Print post
Permalink

Obviously I have been aware of the updates for a while now but the penny
had not dropped on the reasons behind the update until I read the
ajaxian post:

http://ajaxian.com/archives/mootools-call-to-upgrade

currently I run a website under 1.11 which has some customised / changed
things to make it work under SSL for IE (was breaking for IE6 under
certain terms), so a straight drop-in change is going to be impossible.

what are the exact changed bits so I can merge them into my release?

what are the implications of this not being done, does it mean that
window.gecko won't be set and are there any other bits that will fail as
a result of that?

i run the site under 3.6 beta 1 and it seems fine, what shall I be
looking for?

cheers
--
Dimitar Christoff <[hidden email]> - http://fragged.org/

Christoph Pojer

[Moo] Re: firefox 3.6 and mootools 1.1.2 / 1.2.4.2

Reply Threaded More More options
Print post
Permalink

It is actually a very simple fix:
http://github.com/mootools/mootools-core/commit/b33269e771885e7a293017d1714500a4898d3e8a

The detection is used at some places in 1.12. I am not familiar with
1.12 any more but I think it is pretty much the same as in 1.2.x
(Event.relatedTarget etc. => mouseenter).

On Nov 5, 12:01 pm, Dimitar Christoff <[hidden email]> wrote:

> Obviously I have been aware of the updates for a while now but the penny
> had not dropped on the reasons behind the update until I read the
> ajaxian post:
>
> http://ajaxian.com/archives/mootools-call-to-upgrade
>
> currently I run a website under 1.11 which has some customised / changed
> things to make it work under SSL for IE (was breaking for IE6 under
> certain terms), so a straight drop-in change is going to be impossible.
>
> what are the exact changed bits so I can merge them into my release?
>
> what are the implications of this not being done, does it mean that
> window.gecko won't be set and are there any other bits that will fail as
> a result of that?
>
> i run the site under 3.6 beta 1 and it seems fine, what shall I be
> looking for?
>
> cheers
> --
> Dimitar Christoff <[hidden email]> -http://fragged.org/
Dimitar Christoff

[Moo] Re: firefox 3.6 and mootools 1.1.2 / 1.2.4.2

Reply Threaded More More options
Print post
Permalink

lol, is that it?

i could hug you but that's inappropriate :) thanks all the same!


--
Dimitar Christoff <[hidden email]> - http://fragged.org/