You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating a nested tabber like in the README will produce a broken tabber if the parent tabber and the first child tabber have a tab name in common.
The parent tabber's ID is 0.
<tabber>
Default={{#tag:tabber|
Default=This child tabber's ID is 0 too.
{{!}}-{{!}}
Not Default=A
}}
|-|
Not Default={{#tag:tabber|
Default=This child tabber's ID is 1.
{{!}}-{{!}}
Not Default=B
}}
</tabber>
I assume it has something to do with the parent and the first child both having an ID of 0.
I can avoid the bug above if I replace the parent <tabber> with the {{#tag:tabber}} format.
The parent tabber's ID is 2.
{{#tag:tabber|
Default={{#tag:tabber|
Default=This child tabber's ID is 0.
{{!}}-{{!}}
Not Default=C
}}
{{!}}-{{!}}
Not Default={{#tag:tabber|
Default=This child tabber's ID is 1.
{{!}}-{{!}}
Not Default=D
}}
}}
But the parent tabber's ID is no longer 0. I guess the parent is processed last now.
A lot of links on our wiki rely on the parent tab anchors having the same -0 ending, so this isn't great.
The text was updated successfully, but these errors were encountered:
Creating a nested tabber like in the README will produce a broken tabber if the parent tabber and the first child tabber have a tab name in common.
I assume it has something to do with the parent and the first child both having an ID of 0.
I can avoid the bug above if I replace the parent
<tabber>
with the{{#tag:tabber}}
format.But the parent tabber's ID is no longer 0. I guess the parent is processed last now.
A lot of links on our wiki rely on the parent tab anchors having the same
-0
ending, so this isn't great.The text was updated successfully, but these errors were encountered: