Extension talk:TabberNeue

On my wiki, any link to a specific tab shows up as "PageTitle#tabber-TabName". Is there a way to remove the "tabber-" so the link becomes "PageTitle#TabName"?

It can be done with `$wgTabberNeueUseLegacyTabIds` in the latest version. However, you cannot use the same tab name again and it can not be the same as other headings.

Thanks for that, that makes sense. I host my wiki on Miraheze and it's not an option there yet, but this was still very helpful.

If I made a tabber using the <tabber> tags like this:

Example 1

<tabber>
Title1=
...
|-|Title2=
...
|-|Title3=
...
</tabber>

I know that three tabs named "Title1", "Title2", and "Title3" will be made correctly.

But what if I had a tabber written like this?

Example 2

<tabber>
Title1=
...
|-|


Title2=
...
|-|
Title3=
...
</tabber>

I tested this locally on another wiki and found that visually, the tabs do not create extra whitespace. This is inspite of "Title2=" having so much space preceding it, and "Title3=" being written on new line below its separator |-|.

So I would like to know if whitespace is stripped when putting empty line breaks between tab separators |-| and their titles with equal signs =.

If this is the case, I think this is something important to point out under Extension:TabberNeue#Usage because I have seen editors write the separators and titles inline (Example 1), while some write them as blocks (Example 2) for different readability reasons.

EDIT: Here are the specs of the wiki I tested on:

Product	Version
MediaWiki	1.39.0
PHP	8.0.26 (fpm-fcgi)
Vector	1.0.0
TabberNeue	1.7.4

The documentation should also clarify how it handles whitespace *within* the tab name, e.g. is "Title 1" the same as "Title 1".

I'm just upgraded my wiki to 1.38.

Your question is quite vague, there's nothing to "fix" as this is an intentional Tracking category to help users find which pages use the Tabber parser tag {{#Tabber:}} (many extensions do this, and MediaWiki now adds tracking categories automatically to pages in certain circumstances also. This is a helpful feature for site administrators. If you don't want these to show on pages, you might want to read Help:Categories#Hidden categories.

I know this is more than a year later, but, thank you, @TiltedCerebellum! I didn't know I could hide categories! And while it's certainly a useful category for me, as an administrator, I don't necessarily want it cluttering up the bottom of the page where categories are displayed! I've now hidden the category, and it looks great! Thanks, so much!

That's okay, we're both neglecting our emails it seems, lol. You're welcome :)

There's an option in your user prefs to show hidden categories as well, but it won't be displayed by default to users, which is nice.

Sometimes, one may want another tab than the first one to be active initially. Is there any way to denote that with the existing syntax or is currently the only workaround to use JavaScript? If the latter is the case, are there any plans to implement this functionality natively into the extension's supported syntax?

I am using the Citizen skin and it works great. However, with MobileFrontend active and if I put the site in mobile view, the tabs don't work. Is this an issue or am I missing some part of the config for mobile?

It's hard to know what's going on when all we know is that it doesn't work. Do you have a link to a page where under mobile view the tabs are not working?

Is it possible to have the status of two tabber instances linked?

Lets say on the page I have a header section with tabs "Red | Green | Blue"

Then there is some static content.

Then later under a different section we have another set of the same "Red | Green | Blue" tabs.

I'd like the content in each section to change whenever one is selected but the content in the middle between them stay the same.

So selecting "Blue" would show

"Blue content Header"

"Static Content"

"Blue section 2 content"

Is there any way to get TabberNeue working with subst or safesubst? The |-| seems to break things even when escaped. Also, I just updated to the latest code and now this #tag: example given on the extension's page here no longer works:

{{#tag:tabber|
Tab1={{{1|}}}
{{!}}-{{!}}
Tab2={{{2|}}}
}}

I'd have thought my issue stemmed from that, as going back to a prior version makes #tag work again for the above, though it still refuses to work with subst/safesubst. Tried multiple combinations of the following (plus escaping or not escaping =):

• {{!}}-{{!}}
• {{!}}-|
• |-{{!}}

This works only when subst: is removed:

{{subst:#tag:tabber|
Tab1={{{1|}}}
some content
{{!}}-{{!}}
Tab2={{{2|}}}
more content
}}

Thanks for any insight! FrozenPlum (talk) 19:09, 26 April 2024 (UTC)

May I ask which version or commit of TabberNeue are you updating from?

Hey, I'm trying to have a dynamic tab titles, so it gets the title by template params, such as "tab1title", but the syntax does not parse and remain like "{{{tab1title}}}", what should I do?

I have the same Issue, so if there is someone who could help, it would help us both :)

It's been a bit but I think I solved this before by using the {{#tag:tabber|...}} parser.

Hi, I had the same problem with internationalization, i.e. {{int:my custom message}}

I changed the following in /includes/Tabber.php line 123:

before:

$tabName = $parser->getTargetLanguageConverter()->convertHtml( trim( $tabName ) );

after:

$tabName = $parser->recursiveTagParseFully( $tabName );
$tabName = $parser->stripOuterParagraph( $tabName );

That works for me (MW 1.41).

Hope it helps...

This is implemented in the latest version

I've noticed that Tabber, if there's no javascript, displays all tab contents. Tabber Neue seems to instead entirely become hidden, meaning the contents are no longer accessible. Are there plans to make TabberNeue degrade more gracefully?

That is very weird as TabberNeue should also display all tab contents. Do you have an example page with the issue?

I've noticed this happen in one case: the tabber seems to remove all of the other tabs and display all of the tab contents in the first tab when collapsible text is added in one tab.

This is probably something very easily fixed, but I recently migrated a wiki from fandom to miraheze, and every tabber code is broken. The extension is enabled on the wiki, but the coding is still broken. What can be done to fix it?