Skip to main content

Search and Top Navigation

#6019 closed bug (fixed)

Opened September 04, 2010 12:31AM UTC

Closed April 11, 2011 03:17PM UTC

Panel content mismatched to first tab if divs not in same order as list

Reported by: Branik Owned by:
Priority: major Milestone: 1.8.6
Component: ui.tabs Version: 1.8.4
Keywords: Cc:
Blocked by: Blocking:
Description

Sample taken from live generated code view to show that it is applying ui-tabs-hide to divs two and three even though div two (#exercising) should be the content displaying.

<div id="SessioningTabs" class="ui-tabs ui-widget ui-widget-content ui-corner-all">
	<ul class="ui-tabs-nav ui-helper-reset ui-helper-clearfix ui-widget-header ui-corner-all ui-sortable">
		<li class="ui-state-default ui-corner-top ui-tabs-selected ui-state-active">
		<a id="SessionTab_exercise" href="#exercising">Exercising:</a></li>
		<li class="ui-state-default ui-corner-top">
		<a id="SessionTab_train" href="#training">Training:</a></li>
		<li class="ui-state-default ui-corner-top">
		<a id="SessionTab_groom" href="#grooming">Grooming:</a></li>
	</ul>
	<div id="grooming" class="ui-tabs-panel ui-widget-content ui-corner-bottom"> .... panel content
	</div>
	<div id="exercising" class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide"> ... panel content
	</div>
	<div id="training" class="ui-tabs-panel ui-widget-content ui-corner-bottom ui-tabs-hide"> ... panel content
	</div>
</div>

Constantly shows the first div's content under the first tab on page load regardless of which tab is listed first in the ul.

If you click the second or third tab and then go back to the first, the content will then be correct.

I am using this with sortable so my users can select their tab order and have it saved for them so the tabs will display in their preferred order. The ul is dynamically generated by php and can thus be in any order, but this behavior is also the same if you just list the divs in a different order than the li elements in static html and are not using sortable.

This worked perfectly in 1.7.2. The problem showed up in 1.8 and is still present in 1.8.4.

Attachments (0)
Change History (1)

Changed April 11, 2011 03:17PM UTC by scottgonzalez comment:1

milestone: TBD1.8.6
resolution: → fixed
status: newclosed

Fixed in 1.8.6 when #6125 was fixed.