[jQuery] Re: Safari 1.3.2 click event not returning false

2007-08-04 Thread NickMaller
Thanks for the suggestion Klaus, your post lead me to try a few different things and i've found a solution. So what I ended up doing is applying the javascript directly on the onclick attribute for safari only, ie: if($.browser.safari) { $(".banking-window").attr("onclick", "wind

[jQuery] Re: Safari 1.3.2 click event not returning false

2007-08-01 Thread Klaus Hartl
NickMaller wrote: Thanks everyone for your responses, In regards to upgrading to a newer version, it's part of my client's requirements for it to be compatible with this particular combination as it's based on feedback and stats from thier users. It would be a lot simplier if everyone just used

[jQuery] Re: Safari 1.3.2 click event not returning false

2007-08-01 Thread NickMaller
Thanks everyone for your responses, In regards to upgrading to a newer version, it's part of my client's requirements for it to be compatible with this particular combination as it's based on feedback and stats from thier users. It would be a lot simplier if everyone just used 1 browser but thats

[jQuery] Re: Safari 1.3.2 click event not returning false

2007-07-31 Thread Klaus Hartl
Sam Collett wrote: 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' perh

[jQuery] Re: Safari 1.3.2 click event not returning false

2007-07-31 Thread Sam Collett
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

[jQuery] Re: Safari 1.3.2 click event not returning false

2007-07-31 Thread Gordon
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