Thanks Klaus,
That's a fantastically simple workaround. It wouldn't have occurred to
me to put in that redundant loop/function.
I'm not surprised that Safari 1.3 isn't supported by jQuery, trouble
is, most people I develop for think that it should work just as well
regardless! I'll have to debug as I go.
Many thanks again,
Dan.
On 1/9/08, Klaus Hartl <[EMAIL PROTECTED]> wrote:
>
> On 9 Jan., 19:14, "Dan Eastwell" <[EMAIL PROTECTED]> wrote:
> > Thanks Klaus, I'll have to rewrite my functions for that. I'm sure
> > it's no great headache.
>
> Before rewriting, have you tried the following?
>
> // attach event handler the usual way
> var $a = $('a');
> $a.click(function() { ... });
>
> // be nice to Safari 1.3 dinosaurs
> $.each($a, function() {
> this.onclick = function() { return false; };
> });
>
> I think I've done it like that once but cannot remember where to find
> it...
>
>
> > Thanks again for your reply. Do you know how the ui.tabs plug in
> > covers this situation?
>
> Yes. I do not support Safari 1.3 ;-)
>
> I consider this browser as outdated as IE 5 (which is not supported by
> Tabs either). Safari 1.3 isn't officially supported by jQuery itself
> by the way.
>
> --Klaus
>
--
Daniel Eastwell
Portfolio and articles:
http://www.thoughtballoon.co.uk
Blog:
http://www.thoughtballoon.co.uk/blog
