Board Thread:Support Requests - Getting Technical/@comment-1686138-20151206045332/@comment-115.70.239.76-20151206130501

You may or may not be under the wrong impression, however to clarify I am not seeking advice on implementing tabview inside or apart of a portable infobox, but using a portable infobox contained in a page using tabview. Additionally to kick the boot further, using the mw-collapsible function in the exact same manor, however in a classic infobox doesn't break the collapsible function. The issue only exists with a portable infobox

So using it the same say you would any other page, eg. PAGENAME1|TITLE1 PAGENAME2|TITLE2 PAGENAME3|TITLE3 If PAGENAME1 had a portable infobox contained on it's page, then the portable infobox looses some functionality when it's transcribed via. tabview, particularly it's collapsible ability which is the only function that I need.

If you are interested, I have dozens of templates that use both tabber and tabview inside of the infobox, both work flawlessly, eg. Example uses tabber inside of the infobox to change information while the template itself remains the same. Looking at that example page, it's easy to understand why I need to separate duplicate naming of the same content, where only minor details change. To sum it up; 1 enemy with 5 variations depending on where it's encountered, 3 different titles that re-use the same enemy with 5 variations per title. Think of something like Final Fantasy, that has 20 odd titles, with each title having an item called Potion and different variations of Potion depending on where the item is acquired within each title.

That aside, the only issue I have is the outlined issue in my original post. Hope this may explain the issue better.