I'm getting very similar behaviour in Safari and WebKit nightly build with a slideshow widget i'm making with jcarousel. I'm not using google js, just local jquery, and also using the preload plugin to preload my images. (http://plugins.jquery.com/project/Preload)
Seems that when the site is tested on localhost (ie, fast loading times) i get the unexpected behaviour - sometimes jcarousel fails to fire, essentially, so the prev/next buttons don't show and no scrolling happens. If i refresh, sometimes i get expected operation, other times it remains broken. FF and even IE work fine -- it's almost as if Safari/WebKit is too fast... Is there some cleverness about the way it works that disagrees with Jcarousel - but only sometimes? S On Oct 14, 10:23 am, Stephen <[EMAIL PROTECTED]> wrote: > Im using google.load to fire up jquery and it seems that its causing > jCarousel to behave funny in chrome / safari, firstly if the jcarousel > call is before the carousel itself then the next / previous buttons > stay disabled then if you move the call after the carousel then it > lose position and scroll more than it should compared to firefox etc. > > im using the simple template as a debug as the page i am using this on > has allot of other function which i thought to be the problem > originally, here is the code i am using. > > <script language="javascript" type="text/javascript" > src="http://www.google.com/jsapi"> > </script> > <script type="text/javascript"> > google.load("jquery", "1.2.6"); > google.setOnLoadCallback(function() > { > $('#mycarousel').jcarousel({ > vertical: true, > scroll: 2 > });});</script> > > <!-- > jCarousel library > --> > <script type="text/javascript" src="../lib/jquery.jcarousel.pack.js"></ > script> > > Any ideas how to get safari behave for this?