I reported this before - since you can easily reproduce it with the sample code.
But someone removed the thread, so here the archive link: http://www.nabble.com/bugs-with-multiple-fast-tab-clicks-tp23785806s27240p23785806.html On Jun 11, 4:01 am, cwiese <cwi...@gmail.com> wrote: > I have the SAME ISSUE - SAME VERSIONS - my tabs worked prior to > upgrading to Jquery > UI 1.7. > > Now, when using REMOTE (ajax) tabs - if a user click a tab - while > another is loading the Ajax does get called, and the DIV gets > populated but > the CLASS that determines which tab is visible does not every change > for the 2nd click.....the first request is displayed - even though > with firebug I can see the 2nd DIV content is loaded. > > Ugghhhh....working perfectly with the older version of tabs (and > Jquery 1.2.6). > > So, in short....fast clicking is NOT necessary - any remote load > taking > more than 1 second gives the user a chance to click another tabs - > which gets loaded but never displayed. > > The DIV for the 2nd click still has "ui-tabs-hide" and the first > clicked is visible. Has the "queuing" of Ajax calls been changed in > Jquery 1.3x? > > Here is the declaration: > > var $tabs; > $(document).ready( function() { > $tabs = $("#assign-tabs").tabs( { > remote: true, > ajaxOptions: {cache: false}, > spinner:'<em>Loading...</em>', > //toggle - below is ugly > fx : { > opacity: 'show' , > height: 'show', > duration: 'slow' > }, > onShow : function(clicked, shown, hidden) {//(event, > ui) { //TODO > if (jQuery.browser.msie) { > ui.panel.style.removeAttribute > ('filter'); > }; > $(ui.panel).find > (":text:visible:enabled:first").focus(); > } > }); > > }); > > <div id="assign-tabs" align="center" class="ui-tabs-nav"> <ul> > <li> "<s:property value='%{#assign_url_s}' " title="Assign > Standard > Sets">Standard </li> > <li> "<s:property value='%{#assign_url_c}' " title="Assign > Corporate > Sets">Corporate </li> > <li> "<s:property value='%{#assign_url_p}' " title="Assign > Population > Sets">Population </li> > > <!-- class="ui-tabs-disabled" --> > </ul> > <div id="Assign_Standard_Sets"> > "<s:url value='/images/ajax-loader.gif' includeParams='none' > " > width="30" alt="" /> > </div> > <div id="Assign_Corporate_Sets"> > "<s:url value='/images/ajax-loader.gif' includeParams='none' > " > width="30" alt="" /> > </div> > <div id="Assign_Population_Sets"> > "<s:url value='/images/ajax-loader.gif' includeParams='none' > " > width="30" alt="" /> > </div> > </div> > > On Jun 10, 4:47 pm, nextpulse <rob...@nextpulse.com> wrote: > > > jquer - 1.3.2 > > jqueryui - 1.7.1 > > > On May 30, 3:01 am, Klaus Hartl <klaus.ha...@googlemail.com> wrote: > > > > Which version are you using? I've fixed a similiar bug (if not the > > > same) bug a while ago... > > > > --Klaus > > > > On 28 Mai, 19:30, nextpulse <rob...@nextpulse.com> wrote: > > > > > I have 3 tabs that each loads using ajax (via href). > > > > The problem i am having is that while a tab is loading - the user can > > > > click on another tab (as they should). > > > > But the tab panel rendering then gets confused - depending how long > > > > the ajax takes or how quickly the tabs are clicked - the results can > > > > (and do) come back on a different panel. > > > > > Is this a bug or another way around this? > > > > > I don't want to disable the tab - as it is very reasonable for a user > > > > to click on the another tab while one is loading. > > > > > My current workaround is to avoid the ajax in the tab and make a call > > > > via the the 'select'. This works good - but then I lose all the nice > > > > features of the loader info on the tab display (and the cache).- Hide > > > > quoted text - > > > - Show quoted text -
