Safari 2 has some serious problems with it's Javascript interpreter. Any
page that has a heavy amount of Javascript will fail. I know the jQuery team
has to run the jQuery unit tests on Safari 2 in chunks, otherwise Safari 2
blows up. There's several posts about this in the archives.

-Dan

>-----Original Message-----
>From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On
>Behalf Of Jeffrey Kretz
>Sent: Thursday, July 10, 2008 2:39 PM
>To: jquery-en@googlegroups.com
>Subject: [jQuery] Re: Safari 2 Mac - loads of problems!
>
>
>Unfortunately, I too have had a number of problems related to Safari 2, in
>building a CMS system.  I was able to get the public part of the site to
>work, but the CMS administration (HTML Editor, etc) had many many problems,
>despite everything working well in FF, Opera, IE6 and IE7.
>
>Eventually, my boss decided to not support Safari 2, and we've had to tell
>our clients on our CMS who use Safari to switch to Firefox or upgrade to
>Safari 3.
>
>JK
>
>-----Original Message-----
>From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On
>Behalf Of herrflick
>Sent: Thursday, July 10, 2008 10:51 AM
>To: jQuery (English)
>Subject: [jQuery] Safari 2 Mac - loads of problems!
>
>
>I've been working on a site that is really heavy with jquery stuff,
>but have found it almost impossible to get even pretty basic stuff
>working in safari 2 on a Mac.
>
>The development site is at: http://dev2.drfoster.co.uk/
>
>the scripts I've written are at:
>http://dev2.drfoster.co.uk/script/hg-functions.js
>& http://dev2.drfoster.co.uk/script/graph.js, and i'm using jquery
>v1.2.6.
>
>The graphs & all the page functions work as intended in all the
>browsers I need (ie6 + win, firefox 2+, safari 3 mac, safari win etc),
>but in safari 2 Mac the browser originally just crashed. I added
>browser detection and created some basic alternative stuff, but as
>soon as I add more than a few functions, the site stops working.
>
>Has anyone had a similar issue with jquery, safari 2 (and perhaps
>google maps API?)
>
>Thanks for listening!


Reply via email to