Our Platform was recently updated to 11.18.1 and we had issues with the tabs control always returning to the first tab. We implemented this solution, and it fixed the problem for the tab events. But we are now seeing a similar problem when clicking a page on the List_Navigation web block for a table inside the TabsContentItem. When the page button is clicked the Refresh action occurs, but then the CurrentTab is set to 0 and both TabContentItems become visible.
The CSS recommended by the solution I mentioned doesn't work, because the event is on the Content not the Header and placing similar CSS on the Content prevents the button action from happening at all (of course).
It sounds like this is a known issue, but any thoughts on a workaround in the meantime?
Any ideas would be greatly appreciated.
Here's a picture of the end result. Note that both tabs are indicated as active and are visible.
Hello @Kevin Martens
Could you please share a sample so that I can test your particular use case?I'm asking this to make sure that is covered on the fix we did on Tabs under de code ROU-4127 (for future reference on release notes) and that will be released in version 1.12.0 with an ETA of March 27.
Cheers,GM
Thank you for your response and thanks for the quick fix.
Here's the oml file. The problem is happening on the ByCycle page and occurs when any of the actions on the page are called (changing a filter for instance) and the current tab is not the first (0) tab.
Let me know if you need anything else.
Hi @Kevin Martens
I tried to use your module but it has a lot of missing dependencies, giving more than 1300 errors.I tried to replicate it on a module created from scratch and with the new version we'll release next week I was not able to replicate the issue, so I believe it will be fixed. Just attached a GIF to validate the use case you're facing.
Sorry about the missing dependencies.
If you have time, here's a very simple module with a tab that has the same behavior.
Change the tab and push the ok button. On version 1.11 the ajax refresh on the button will leave the content for both the tab you clicked and the first tab ('Personal', tab 0).
If this module works properly on 1.12 then everything should be fine with our other pages that have tabs.
Thanks again.
Thank you for sharing, it was super useful đŸ™‚
Based on my tests using the version that will be released next week I think it's safe to say that it will be fixed with what we did under the code ROU-4127 (for future reference on release notes) and that will be released in version 1.12.0 with an ETA of March 27.
Best Regards,GM
Could you put the content of the "tab" into a block? then the pagination will be inside the block, and dont will change the screen (where is the tab header).
Thank you for your suggestion. Unfortunately, the behavior is the same.
It looks like the Tabs Web Block javascript function onTabsClick triggers no matter what is clicked inside the Tabs Web Block. That make sense. It seems like it is not getting the data-tab attribute from the correct element. Alexander Stump mentioned this same issue here.
Here's the function if that helps. Sorry, I had to take a picture, because cut and paste made a mess.