Found that when a class is set on a tab content element, it breaks the tabs.
Original example that Syncfusion supplied to a forum thread:
Forked example but with a class added to each tab content element:
Tab content with class (stackblitz.com)
It looks like when the tab content element gets initialized, the 'e-item' class gets appended on to whatever class is already set on the tab content element ("tabBodye-item" instead of "tabBody e-item"). This breaks the functionality of the tabs.
I'm initializing my tabs using HTML elements, but then programatically hiding / showing tabs after a dropdownlist selection based on data-* attributes in the tab content elements and the index of said element in all of the tab content elements. I'm able to work around it but found it to be an odd behavior and thought it should be fixed.
|
<div id="tabContainer">
<div class="e-tab-header"> <div><span id="tabHeaderIdea">Tab1</span></div> <div><span id="tabHeaderProject">Tab2</span></div> </div> <div class="e-content"> <div class="tabBody ">...content tab 1</div> <div class="tabBody ">...content tab 2</div> </div> </div> |
That works, just like another work around that I was able to use. But you guys are going to fix the issue in a future release, correct?