While in an ideal world, people would update their browser, sometimes
it is not a viable choice (does Safari 2 even work on OSX 10.3.x?) and
may even alienate users (imagine how much easier it would be if all
IE6 users went to IE7 or Firefox?).
Rather than 'return false' perhaps e.preventDefault will work (I don't
have any version of Safari, so can't test)?
("#foo").click(
function(e) {
e.preventDefault();
.....
On Jul 31, 9:06 am, Gordon <[EMAIL PROTECTED]> wrote:
> How does it work in newer versions of Safari? If it works in 2.x or
> 3.x then this is more than likely a browser bug rather than a problem
> with jquery in which case you should advise your client to upgrade
> their browser.
>
> On Jul 31, 1:53 am, NickMaller <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> > I have the below problem happening for one of my clients, any ideas on
> > what's the cause? I've tried a number of different things and
> > essentially updating to the latest nightlie and removing all other
> > javascript except for the return false on the link and the problem
> > still persists.
>
> > Bug Details:
> > Safari 1.3.2 on OSX 10.3.9 using older version of jquery (but have
> > tested with 1.1.3.1 with same result) does not return false on the
> > click event defined.
>
> > Offending
> > URL:http://secure.heritageonline.com.au/OffendingJS:http://secure.heritageonline.com.au/media/javascript/jquery.heritage.js
> > on line 66
>
> > In some cases the return false works the first time it is clicked but
> > fails after that. In some cases it doesn't work the first time at all.
