my temporary solution : eval.call(window, data) to eval(data) in jquery.js in function globalEval
Any idea, how to bypass around this bug more correctly until fox 3 release ? On Nov 28, 2:22 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I'm sure by the time Firefox 3 is released to the general public this > issue will be resolved. Having said this: Firefox 3 is more stable > that Firefox 2.0.0.10 on my computer. > > On Nov 27, 10:28 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > > Hi! I have same problem. Is there already some solutions in that way? > > > On Nov 23, 4:58 pm, Cloudream <[EMAIL PROTECTED]> wrote: > > > > ff3 just in beta. jorn is working at mozilla, so don't worry about > > > this... > > > > On Nov 23, 4:44 pm, Jerome Carty <[EMAIL PROTECTED]> wrote: > > > > > Just a note: > > > > > On AJAX calls where the data type is script, I get the following > > > > error: > > > > > EvalError: function eval must be called directly, and not by way of a > > > > function of another name > > > > > This error is triggered from line 501 of jquery 1.2.1 uncompressed. > > > > > By the way, when an error is thrown, the exception parameter is always > > > > undefined for me.
