my 2ct contribution to this discussion. FF 2.0 & firebug 1.0beta cause a lot of problems - even on sites without jQuery :) so often the debugger pops up and interrupts some scripts (didn't investigate why). sometimes you can resume - but mostly the script is broken. switch back to firebug 0.4 everthing is fine. at least i can say that my jq-scripts (mostly ajax stuff) run great on IE6.0, IE7.0, Mzille1.8, FF1.5 and also FF2.0 (without firebug 1.0 installed) - but with firebug beta it crashes. so we'll wait for the release...
offtopic question: unfortunately it's not possible to have two or more versions of firefox on the same machine - the new windows installer uninstalls all older versions prior to FF2.0 :(( - or did you know a possibility to have both versions (FF1.5 & 2.0) installed on one machine? older mozilla/ff versions are also available as a ZIP archives wich can be copied to any programs folder without any installation. stefan > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Kelvin Luck > Sent: Thursday, December 14, 2006 10:48 PM > To: Jörn Zaefferer > Cc: jQuery Discussion. > Subject: Re: [jQuery] Fix: ExternalInterface breaks jQuery in > firefox 2 > > Jörn Zaefferer wrote: > > Kelvin Luck schrieb: > >> * Calling an ExternalInterface function which passes arguments > >> between Flash and JS in Firefox 2 breaks the a.constructor==String > >> comparison ( see http://dev.noiseusse.org/testflash ). > >> > >> * This then totally breaks jQuery which relies on this > comparison (in > >> the find function for one). > >> > > That site works great for me with FF 2.0. And yes, there > are no more > > a.constructor == String comparions in jQuery core. Only Array and > > Boolean, are they an issue, too? > > > > Have you got firebug installed? The alerts make it seem that > it's working but the console.log statements make the problem clear... > > And while there may not be any constructor == String > comparisons in the jQuery core it looks like there are still > a few constructor != String comparisons which suffer from the > same problem. > > Afaik there is no issue with Array and Boolean comparisons... > > Thanks for the feedback, > > Kelvin :) > > _______________________________________________ > jQuery mailing list > [email protected] > http://jquery.com/discuss/ > _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
