Comments on: MooFlow Firefox Uncaught Exception Fix

By: BriAnn

BriAnn — Mon, 27 Jul 2009 23:25:23 +0000

Wow, lizux that worked great for me too in mootools 1.2.3, reflections are there. Only problem I’m having now is the bridge with ReMooz.

By: Fonsan

Fonsan — Thu, 02 Jul 2009 14:58:13 +0000

Thanx a bunch, saved me some time

By: lizux

lizux — Wed, 29 Apr 2009 05:36:27 +0000

// just change this to the one below
// var i = arg.img.clone();
var i = arg.img.clone().set(’src’, arg.img.src);
and this works fine in mootools 1.2.1

By: mgsmus

mgsmus — Thu, 09 Apr 2009 09:11:42 +0000

Thanks. That solved error but i can’t see any reflection in FF, but demos at mooflow are working good. Any idea?

By: Jason

Jason — Sat, 04 Apr 2009 14:37:33 +0000

Hi Benson,

I have experienced similar issues with the latest firefox. In my experience, my code would retrieve values set in another frame several times, then at the end of the function it would fail to do more of those operations. At some point in time, it was as though the window object had become corrupt.

The way I solved it was to define a variable at the very top of my function that would contain the reference to the window object. This solved it for me.

Hope this helps.

By: benson bear

benson bear — Sat, 04 Apr 2009 07:15:46 +0000

Hey, how about that other stupid exception trying to open a frame’s document and write into it in the newest Firefox? I am getting that too all of a sudden in similar cirucmstances but noone else seems to be. Have you found out what it is?

I can open lots of iframe documents and write into them, just not some. Cant see the difference

By: Primalmotion

Primalmotion — Wed, 01 Apr 2009 08:11:14 +0000

Thanks dude!