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 in an ideal
world like Sam mentioned.
I've tried using e.preventDefault() previously and it helped slightly
(ie. it worked more time than what it was previously) but ultimately
the bug still pops up. If it's a problem with that version of safari
and the addEventListener is there an alterntive way that should be
used in the jquery code to address this?
Thanks again
-Nick
On Aug 1, 1:14 am, Klaus Hartl <[EMAIL PROTECTED]> wrote:
> 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' perhaps e.preventDefault will work (I don't
> > have any version of Safari, so can't test)?
>
> > ("#foo").click(
> > function(e) {
> > e.preventDefault();
> > .....
>
> I remember slightly that this is simply a browser bug that occurs when
> attaching events via addEventListener...
>
> --Klaus
