[jQuery] Re: Safari + triggerTab() = fail

[ZAP]

Thanks for your reply. I'm not using the History plugin, however (just
trying to add back and next tab links within the tabs themselves, not
back or next in terms of browser history). So this probably isn't
related to History, right?

Would it be worth trying UI Tabs instead? I haven't done that so far
because everything is working well throughout the site except for this
blasted Safari bug, and I don't want to make trouble for myself
unnecessarily. Is the process of converting to UI Tabs as easy as
switching the script file?

Thanks again!


On Mar 11, 3:27 pm, Klaus Hartl  wrote:
> History is broken in Safari 3, one of the reasons it was taken out of
> UI Tabs.
>
> --Klaus
>
> On 11 Mrz., 21:46, ZAP  wrote:
>
> > Hello -
>
> > I'm using Klaus' Tabs plugin (Version: 2.7.4) with jQuery 1.2.6, but
> > the triggerTab() function just isn't working for me in Safari 3. No
> > matter how I create Back and Next buttons or links, Safari instead
> > tries to load a new page (e.g.,http://mydomain.com/?#start) instead
> > of switching tabs. Clicking the tab headers works as expected in
> > Safari, and everything works properly in all other tested browsers.
>
> > I've tried various methods to make these links work in Safari, such
> > as:
> >  > onclick="$('#formtabs').triggerTab(1);return false;"/>
> > « back
>
> > What might be the cause of this, and more importantly what might be
> > the solution?
>
> > Thanks in advance for your replies.
>
> > ZAP
>
>

[jQuery] Safari + triggerTab() = fail

[ZAP]

Hello -

I'm using Klaus' Tabs plugin (Version: 2.7.4) with jQuery 1.2.6, but
the triggerTab() function just isn't working for me in Safari 3. No
matter how I create Back and Next buttons or links, Safari instead
tries to load a new page (e.g., http://mydomain.com/?#start) instead
of switching tabs. Clicking the tab headers works as expected in
Safari, and everything works properly in all other tested browsers.

I've tried various methods to make these links work in Safari, such
as:

« back

What might be the cause of this, and more importantly what might be
the solution?

Thanks in advance for your replies.


ZAP

[jQuery] Re: random option for Cycle not working?

[ZAP]

Thanks for your reply. I was using the compressed version of 2.01
(with all transitions). I thought that I'd fixed the problem yesterday
by switching to the uncompressed version. It did fix it, but just now
I tried the latest (2.09) compressed version and it also works. So I
guess there was a bug in 2.01 in particular and it's fixed in 2.09. I
didn't notice that my version wasn't the latest until you asked the
question. What confused me was that I thought that it had been working
before, but now I believe that I was just misremembering things again.


On Jan 30, 5:52 pm, "Mike Alsup" <[EMAIL PROTECTED]> wrote:
> What version of the plugin?
>
> On Jan 30, 2008 1:26 PM, ZAP <[EMAIL PROTECTED]> wrote:
>
>
>
> > For some reason, Cycle is not randomizing the order of my blurbs.
>
> > 
> > $(document).ready(function(){$('#blurbs').cycle({fx:'turnDown',random:
> > 1,timeout:1});});
> > 
>
> > Anyone know why this might be?

[jQuery] random option for Cycle not working?

[ZAP]

For some reason, Cycle is not randomizing the order of my blurbs.


$(document).ready(function(){$('#blurbs').cycle({fx:'turnDown',random:
1,timeout:1});});


Anyone know why this might be?

[jQuery] AJAX load syntax question

[ZAP]

I'm wondering if there's a way to pass AJAX POST vars with a key
that's assigned as a variable, e.g.

function updateQty(uniqueID,qty){
$("#basket").load("/basket-contents.html",{uniqueID:qty});
}

What I'd like to get from this is a POST var with a key of whatever
the variable uniqueID is, but what I get is a POST var called
"uniqueID".

It seems like there must be a syntax for doing this that I just don't
know, right?

[jQuery] Re: $.load() POSTing instead of GETing

[ZAP]

I also ran into this problem, and it was truly vexing. I was trying to
POST
to an XML file (dynamically generated by PHP), and the server didn't
allow
that so no POST vars were being received. Very glad I stumbled across
this
post, since otherwise I'd probably be hacking together a GET version
or
using the ajax call with a success function or some other difficult
kludge
like that right now.

On Aug 18, 5:15 pm, Stephan Beal <[EMAIL PROTECTED]> wrote:
> One of the negative side-effects is, however, thatPOSTisnot
> configured consistently across servers. For example, i had the example
> same problem as the OP... i was trying to load() an HTML file and it
> worked onmylocal system. When, however, i uploaded it tomyhoster
> the code suddenly failed.FirebugrevealedthatPOSTwaserroringout
> onmyhosterbecausePOSTwasnotallowedfor HTML files on that
> server. So i had to rework the code to use get(). i remember trying to
> set GET as the default ajax behaviour and that load() ignored that.