Extension talk:Header Tabs

Header Tabs sometime fails to load

Ever since we upgraded to MW1.35 it sometimes happens that opening a page that uses multiple headers fails to load properly.

Everything is on the page and the tabs are also on top but all the page content is shown below the first header. The tabs do not work.

When you go back one page and click on the link again or use F5 the page loads normally and after that it seems to keep working until time X has passed.

I get the fault Exception in module-execute in module ext.headertabs (see screenshot) and I tried to figure out what is going on but I am not sure where to look first.

Can someone please push me in the right direction :-)

Felipe (talk) 12:04, 14 January 2021 (UTC)

Nice work getting that screenshot ready for public viewing! Are you using the latest version of Header Tabs? Also, I would recommend adding "?debug=true" (or "&debug=true") to the URL, then reloading until the error happens - the error message in the console may be more helpful. Yaron Koren (talk) 13:59, 14 January 2021 (UTC)

Well it is not up to me, it is our company wiki :-)

I tried lots of times with the links and adding ?debug=true but it does not want to fail.

Then it happened when using &action=purge. On some pages we use a link with &action=purge to force a Sematic update.

The below code was in de Console, maybe this helps. I will try tomorrow with the debug option and dig some more.

POSThttp://internalwiki.blabla.com/internalwiki/index.php?title=Somepage&action=purge
[HTTP/1.1 302 Found 1227ms]
GEThttp://internalwiki.blabla.com/wiki/Somepage
[HTTP/1.1 200 OK 6804ms]
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. Somepage
GEThttp://internalwiki.blabla.com/internalwiki/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector
[HTTP/1.1 200 OK 0ms]
GEThttp://internalwiki.blabla.com/internalwiki/load.php?lang=en&modules=ext.jquery.async%7Cext.libs.tippy%7Cext.smw%7Cext.smw.purge%2Ctooltips%7Csmw.entityexaminer%2Ctippy&skin=vector&version=1gv35
[HTTP/1.1 200 OK 0ms]
GEThttp://internalwiki.blabla.com/internalwiki/load.php?lang=en&modules=ext.headertabs%7Cext.pageforms.autoedit%7Cjquery%2Coojs%2Coojs-ui-core%2Coojs-ui-widgets%2Coojs-ui-windows%2Csite%7Cjquery.client%2CmakeCollapsible%2Ctablesorter%7Cmediawiki.String%2CTitle%2Capi%2Cbase%2Ccldr%2CjqueryMsg%2Clanguage%2Cutil%7Cmediawiki.language.months%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.ready%2Cstartup%7Cmediawiki.page.watch.ajax%7Coojs-ui-core.icons%2Cstyles%7Coojs-ui-widgets.icons%7Coojs-ui-windows.icons%7Coojs-ui.styles.indicators%7Cskins.vector.legacy.js%7Cuser.defaults&skin=vector&version=1yorw
[HTTP/1.1 200 OK 0ms]
JQMIGRATE: Migrate is installed with logging active, version 3.1.0 load.php:147:171
Exception in module-execute in module ext.headertabs: load.php:2:530
TypeError: items[i].toggle is not a function
    updateHiddenState jQuery
load.php:2:567
GEThttp://internalwiki.blabla.com/internalwiki/logos/internalwiki.ico
[HTTP/1.1 200 OK 0ms]
GEThttp://internalwiki.blabla.com/internalwiki/resources/src/mediawiki.skinning/images/magnify-clip-ltr.svg?8330e
[HTTP/1.1 200 OK 0ms]

Felipe (talk) 16:56, 14 January 2021 (UTC)

Okay - it's not surprising that this error message does not show up in debug mode. It sounds like a timing problem (some JS is getting called before it is defined), and the timing is quite different in debug mode. What version of Header Tabs are you running? Yaron Koren (talk) 17:21, 14 January 2021 (UTC)

I updated the all extensions early December 2020, Header Tabs has version: 2.0 (adfd26a)

Wiki config:

Product	Version
MediaWiki	1.35.0
PHP	7.3.23 (cgi-fcgi)
MariaDB	10.4.11-MariaDB
ICU	64.2
Elasticsearch	6.5.4

Felipe (talk) 18:23, 14 January 2021 (UTC)

Alright. My guess is that the Header Tabs lack of display is a symptom of a problem with some other extension or skin... that error message, "items[i].toggle is not a function", doesn't seem to relate to anything in the Header Tabs code. Actually, I have no idea what that is coming from. If you create a wiki page with just tabs, or just tabs and text, do the tabs ever fail to load? Yaron Koren (talk) 15:47, 15 January 2021 (UTC)

Okay maybe this helps, I can reproduce the fault on our TestWiki by purging a page with ?action=purge.

Then I disabled all extensions one at a time until I found out that when disabling the Page Forms extension the page loads normally and I can not reproduce the fault anymore.

I have done this several times, disabling and enabling Page Forms and the fault can only be reproduced when Page Forms and Headertabs are both enabled.

I tried to do the same on the SMW Sandbox Page but I only managed to reproduce this a couple of times. See screenshots below.

I just tried it again by pressing purge page on https://sandbox.semantic-mediawiki.org/wiki/Utilisateur:Jongfeli and it failed again.

It seems that somehow after "X" time a purge page can results in this fault.

Felipe (talk) 13:57, 18 January 2021 (UTC)

Okay, today I updated both Headertabs and Page Forms to Master and suddenly it does not matter if Page Forms is enabled or not, the fault always appears.

To make a long story short, Page Forms has "nothing" to do with it (but I am not sure about this).

When you use Page Forms Master and Headertabs release 1_35 it works just fine.

The page now reports This page is using the deprecated ResourceLoader module "jquery.ui". Please use OOUI instead. but it works just fine.

I assume the move in Headertabs from jquery.ui to OOUI is somehow causing this problem after a page has been purged with &action=purge.

Maybe it has something to do with the fact that a &action=purge is now done with POST that needs to be confirmed.

I did find the items[i].toggle in the below js script.

For now the 1_35 version of Headertabs fixes the problem with an added bonus, we have our familiar blue tabs back :-)

    OO.ui.StackLayout.prototype.updateHiddenState = function (items, selectedItem) {
      var i,
      len;
      if (!this.continuous) {
        for (i = 0, len = items.length; i < len; i++) {
          if (!selectedItem || selectedItem !== items[i]) {
            items[i].toggle(false);
            items[i].$element.attr('aria-hidden', 'true');
          }
        }
        if (selectedItem) {
          selectedItem.toggle(true);
          selectedItem.$element.removeAttr('aria-hidden');
        }
      }
    };

Felipe (talk) 16:17, 19 January 2021 (UTC)

Thank you for investigating this - including finding that part of the JavaScript code. All of what you're saying makes sense, but I can't reproduce the problem, with MW 1.35 and the latest Header Tabs code. Does this happen for you with every page that uses Header Tabs - even a very simple one? Yaron Koren (talk) 15:05, 20 January 2021 (UTC)

No it does not happen on every page, only on pages with multiple tabs (6 to 12) which contain SMW queries.

They take relatively long to load +/- 5 to 10 seconds. Like the example on the SMW sandbox.

See: https://sandbox.semantic-mediawiki.org/wiki/Utilisateur:Jongfeli

On the SMW sandbox site it only happens sometimes, not every time you purge a page. So there is definitely something going on.

I will test some more in the SMW sandbox, maybe we can get it to fail all the time. Felipe (talk) 16:46, 20 January 2021 (UTC)

I doubt that you can ever get some page to fail all the time, since this sounds like a timing-related issue. I wonder, though, if you can figure out what the simplest page is that will sometimes fail. Are SMW queries always required, for example? Yaron Koren (talk) 17:58, 20 January 2021 (UTC)

I do not know if SMW queries are required, I do not think so. like you said it has probably something to do with timing.

Today I tried to figure out what the difference is between pages that work and pages that don't.

I thought I found it when I noticed there where UseCDNCache: "false" codes in the cookie request when it worked and not when it failed.

Maybe it has something to do with it but I am not sure, it was introduced in MW-1.34 see: Manual:$wgUseCdn

The only thing that really helped was disabling the HTTP cache in the Firefox debug mode, then it always loads correctly (but takes forever).

This would suggest there is sometimes something wrong with caching or cookies. Felipe (talk) 15:50, 21 January 2021 (UTC)

@Jongfeli - Where did you land on this? I am experiencing it too. Revansx (talk) 17:14, 15 September 2022 (UTC)

Hello @Revansx. We reverted back to an older version of Header Tabs with the old style tabs not using OOUI.

But also this older version does not work correctly all the time and sometimes only loads the first tab but it does not break the page like the more recent versions and as shown in the screenshot above. This is on MW 1.35.6 I am not sure which version this is, it says 1.3 but that is probably not correct.

I did not investigate any further but the problem is probably still there when using master.

Are you using SMW as well? Felipe (talk) 10:21, 20 September 2022 (UTC)

Hi @Jongfeli, thanks for responding. Sounds like we're in the same boat. Yes, I use SMW as well. The HeaderTabs mainatiners don't seem to be able to reproduce this problem and so it has been suggested that this issue may only manifest when HeaderTabs is used with some other extension (maybe SMW, but we can't actually say which until we can reliably re-produce the problem) .. That said it seems clear that the problem has not been solved.

When it does glitch, it doesn't seem to produce any errors or diagnostic info, so my my new strategy is to seek help from the HeaderTab developers for help in adding some debugging tools in the extension. I'll provide an update here if I am able to make any progress on this problem. Please do likewise. Cheers! Revansx (talk) 17:46, 20 September 2022 (UTC)

Unfortunately the SMW sandbox site is still down. I was able to reproduce it there to. Felipe (talk) 08:51, 21 September 2022 (UTC)

SMW Sandbox Ref: https://sandbox.semantic-mediawiki.org/ Revansx (talk) 20:43, 21 September 2022 (UTC)

Ref: https://phabricator.wikimedia.org/T318286 Revansx (talk) 21:11, 21 September 2022 (UTC)

For MW 1.34.x + HeaderTabs 1.3 + SMW 3.2.3, we were finally able to solve the HeaderTabs issue where the header tabs don't always load. To do so we had modified: /opt/htdocs/mediawiki/extensions/HeaderTabs/HeaderTabs.hooks.php from:

     85                 $resourceLoader->register( [
     86                         "ext.headertabs" => [
     87                                 'localBasePath' => $htDir,
     88                                 'remoteExtPath' => 'HeaderTabs',
     89                                 "scripts" => "skins/ext.headertabs.core.js",
     90                                 "dependencies" => [
     91                                         $jquiTabsModule
     92                                 ]
     93                         ]
     94                 ] );

to

     85                 $resourceLoader->register( [
     86                         "ext.headertabs" => [
     87                                 'localBasePath' => $htDir,
     88                                 'remoteExtPath' => 'HeaderTabs',
     89                                 "scripts" => "skins/ext.headertabs.core.js",
     90                                 "dependencies" => [
     91                                         $jquiTabsModule,
     92                                         "ext.smw.tooltips",
     93                                         "ext.smw.style"
     94                                 ]
     95                         ]
     96                 ] );

specifically we added the SMW resources "ext.smw.tooltips" and "ext.smw.style" as dependencies for Headertabs and that seems to have solved the issue. (fingers crossed) Revansx (talk) 03:14, 28 September 2022 (UTC)

@Revansx does this solution still work for you? I tried and on some pages, HeaderTabs still breaks. In the pages where it breaks, I inspected the page source and realized that the CSS modules for headerTabs does not load on those pages. In particular, this link tag is missing:

<link rel="stylesheet" href="/mediawiki/load.php?lang=en&amp;amp;modules=ext.headertabs.styles%7Cjquery.tablesorter.styles%7Cmediawiki.widgets.styles%7Coojs-ui-core.icons%2Cstyles%7Coojs-ui.styles.indicators%7Cskins.vector.styles.legacy&amp;amp;only=styles&amp;amp;skin=vector"> Fgneba (talk) 19:25, 14 November 2022 (UTC)

We are also running in this problem. Was there in MW 1.31 and is still there in MW 1.35. On arbitrary pages, eg. https://www.geschichtewiki.wien.gv.at/Hofball you should no be able to see the QR code on the right, it should bin in the HeaderTab. Reoloading loads the page just fine. It does not have anything to do with the QRLite extension. Krabina (talk) 07:28, 8 February 2023 (UTC)

Okay I just want to write this down so I don't forget and in the hope that others will recognize this.

We still have the above problem after upgrading MW and all extensions (MW-1.39.5 / PHP 8.1.24) but we have noticed a couple of things:

• It is only a real problem when working from home via a (slower) VPN connection compared to a wired office workplace.
• It "only" happens when using Firefox. Chrome and Edge do not seem to be affected by it.
• It happens mostly on "heavy" pages that take longer to load because of bigger result sets for SMW and Externaldata queries.
• When requesting the page again with CTRL-F5, bypassing browser cache it loads just fine.

I can click around in Chrome and Edge but the problem never pops up. In Firefox it is very easy to break the header tabs. So it seems that Firefox is handling what to load when from cache differently then Chrome or Egde. The result, when I am correct, is that the JavaScript libraries are not loaded yet when the tabs are being generated. Felipe (talk) 07:32, 11 October 2023 (UTC)

Hi there,

Wanted to add my two cents as we have been struggling with this exact issue for years now. We have just upgraded to 1.39.x with HeaderTabs 2.2.2. We use SMW but not on all tabs. We are currently experiencing this issue. I'm seeing it in chrome regularly so i know it's not a browser issue, but it does seem related to cache. I've noticed that having the Dev tools open in chrome will usually not cause the issue (with or without "disble cache" checked ¯\_(ツ)_/¯ ). When the tabs fail to load properly I have the following error in console:

Exception in module-execute in module ext.headertabs:
load.php?lang=en&modules=startup&only=scripts&raw=1&skin=timeless:1 Error: Widget not found
    at OO.ui.Element.static.unsafeInfuse (load.php?lang=en&modules=jquery%2Coojs-ui-core%2Coojs-ui-widgets&skin=timeless&version=1d5er:151:780)
    at OO.ui.Element.static.infuse (load.php?lang=en&modules=jquery%2Coojs-ui-core%2Coojs-ui-widgets&skin=timeless&version=1d5er:151:545)
    at OO.ui.infuse (load.php?lang=en&modules=jquery%2Coojs-ui-core%2Coojs-ui-widgets&skin=timeless&version=1d5er:148:16)
    at <anonymous>:362:19039
    at mw.loader.implement.css (<anonymous>:364:617)
    at runScript (load.php?lang=en&modules=startup&only=scripts&raw=1&skin=timeless:11:983)
    at Array.<anonymous> (load.php?lang=en&modules=startup&only=scripts&raw=1&skin=timeless:12:948)
    at flushCssBuffer (load.php?lang=en&modules=startup&only=scripts&raw=1&skin=timeless:4:956)

So, yeah, it's still happening! We have the issue on many of our wikis, different skins, lots of different extensions.

Hope this helps at all... Jeremi Plazas (talk) 11:08, 7 June 2024 (UTC)

Another point, maybe an observation that's already been tested. I made a simple page with ONLY tabs and plain text. No issue, ever. I added ONE SMW #show function on one of the tabs. After a couple of page reloads the issue appeared.

SMW x HeaderTabs = SometimesTab?

The sad thing is that when we were on 1.35 with HT 2.2, the issue had disappeared for a while. It's only after upgrade to 1.39 that it came back for us. Jeremi Plazas (talk) 11:19, 7 June 2024 (UTC)

We've been investigating this issue some more with our IT director and we noticed a few more things that are definitely of interest:

• The issue goes away when dev tools are open in Chrome and the cache is disabled.
• A similar issue happens with large forms made with PageForms, where the form does not fully load, the loading spinner gets stuck, but the issue also goes away when dev tools are open in Chrome and the cache is disabled.
• A similar issue happens with this embedded code we have for a Benchmark mailing list, where it gets loaded outside of the dom, at the bottom of the page. This issue also goes away when the dev tools are open in Chrome and the cache is disabled.
• Looking more closely at HeaderTabs specifically, we noticed that putting a timeout function of 500ms around the call for OO.ui.infuse right at the top of ext.headertabs.core.js ALSO fixes the issue.

CONCLUSION:

Something is going on with loading time/order. Is there a away to make sure the tabs are infused into the DOM after oo.ui has fully loaded? Maybe I'm missing the mark but you devs find this useful in some other way?

Thanks so much for all the good work! Jeremi Plazas (talk) 13:53, 2 July 2024 (UTC)

That is very interesting indeed - thanks for doing this detective work. Fixing the timing would indeed be the ideal solution, but, barring that, I'm curious about that last solution you found - delaying the "infuse" call. Could you put here the exact code you used? Maybe it's worth just adding that call if SMW is installed. Yaron Koren (talk) 01:04, 4 July 2024 (UTC)

Literally all we did was wrap it with a setTimeout function:

setTimeout(function(){ 
   var tabs = OO.ui.infuse( $( '.mw-tabs' ) );
}, 500);

Jeremi Plazas (talk) 22:06, 4 July 2024 (UTC)

After trying this I understand better what is happening. When completely disabling // var tabs = OO.ui.infuse( $( '.mw-tabs' ) ); the actual tabs are build but the content for each tab stays below the first tab. This is of course not the solution but what happens when you add the setTimeout suggested by JeremiPlazas you delay the moment the content of the tabs is "moved" to the related tab. If you increase the timeout to lets say 10 seconds (10000) the page initially loads completely with all the tab content below the first tab. After the timeout, in this case 10 seconds, you see the page content for the different tabs pop into place.

This means that without timeout this "moving" the tab content happens to soon and before the actual tabs are created. I say moving the content because it looks that way. I do not know how Mediawiki (re)generates a page (HTML) with data from the server and cached data but var tabs = OO.ui.infuse( $( '.mw-tabs' ) ); seems to runs client side and is loaded to soon. So disabling caching altogether will solve the problem because all is coming from the server. This is not a workable solution because your wiki will become very slow. Is there not a way to initiate var tabs = OO.ui.infuse( $( '.mw-tabs' ) ); the moment the page is completely loaded instead of the timeout? Felipe (talk) 06:36, 5 July 2024 (UTC)

Yes exactly! +1 to that. Jeremi Plazas (talk) 11:39, 5 July 2024 (UTC)

You could try calling this:

    $( document ).ready(function() {
        var tabs = OO.ui.infuse( $( '.mw-tabs' ) );
    });

Let me know if that works for you. Yaron Koren (talk) 13:34, 5 July 2024 (UTC)

I have tested this and I can not get it to fail anymore. If other users can confirm this then the $( document ).ready(function() fixes the problem, thanks :-) Felipe (talk) 07:30, 8 July 2024 (UTC)

This seems to resolve the issue for us too. Thanks! Jeremi Plazas (talk) 08:55, 9 July 2024 (UTC)

Okay - that small code change didn't work for all functionality, it turns out; but I just checked in a similar code change that hopefully fully works. If you try out the latest code, please let me know if there are any issues! Yaron Koren (talk) 16:15, 9 July 2024 (UTC)

With 2.2.2 (46f2ae8) I can not get it to fail anymore. Thanks Yaron :-) Felipe (talk) 05:56, 10 July 2024 (UTC)

Great! Sorry it took three years. :) And thanks to everyone for their persistence! Yaron Koren (talk) 14:09, 10 July 2024 (UTC)

Disable on Print Pages

When you print a page that uses header tabs, it only prints the tab that is selected.

Is there some simple CSS that one can add to Print.css that will print all tabs?

Revansx (talk) 00:30, 8 April 2021 (UTC)

<pdf> embed fails to load document on all but first tab

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I use the PDFEmbed extension. The pdf viewer is displayed and the document loads under the default tab. The pdf viewer is displayed but the document fails to load under all other tabs. When the markup is configured to display the second page of the document (e.g., <pdf page=2>File:filename.pfd</pdf>), the pdf viewer is still blank showing page 1/1 until one of the viewer resize buttons is clicked. This forces the viewer to load and display the document. Again, the viewer appears and correctly loads pdf documents only under the first tab. All other tabs display a blank viewer until clicking a button on the viewer (e.g., resize), which then causes the document to load and display properly.

It would appear that the markup is fully executed only for the default header tab page. Is there a way to force complete execution of markup content under all header tabs on the wiki page? Zed4242 (talk) 23:52, 6 May 2021 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

HeaderTabs fail to render image in tab

in previous versions of HeaderTabs (before 2.0), this worked

= [[Image:Task.png|16px|link=]] Tasks =

in the current version in MW 1.35, the images are not displayed, but the img-tag is shown instead. Krabina (talk) 15:02, 16 June 2021 (UTC)

Notices: Undefined index displayed in latest version

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Notice: Undefined index: HTTP_HOST in /extensions/HeaderTabs/includes/HeaderTabs.php on line 228

Notice: Undefined index: REQUEST_URI in /extensions/HeaderTabs/includes/HeaderTabs.php on line 231 Krabina (talk) 09:05, 18 June 2021 (UTC)

I had hoped that the new version 2.1 fixes the issue, however it does not. I am on MW 1.35.x [[kgh]] (talk) 20:54, 24 September 2021 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

HeaderTabs always fail after migration to 1.35

I migrated Mediawiki to following versions:

MW: 1.35.2

SMW: 3.2.3

PageForms: 5.2.1

Skin Pivot: 2.3.0

PHP: 7.4.21

HeaderTabs: 1.3

It shows only the first Tab and the layout is screwed up. I checked the other posts in here but I think the problem is another one. Well, I am a newbie on SMW.

I get 2 errors in the javascript console:

Error: Unknown module: jquery.ui.tabs

...

Uncaught ReferenceError: wgNamespaceNumber is not defined

...

Does anyone have a clue where the problem could be. My intention was first that the problem could be the skin but also other skins show the same result.

Urs Urarku (talk) 23:36, 29 August 2021 (UTC)

New 'bootstrap' style

I edited the 'timeless' stylesheet to fit better in a Bootstrap site (with Chameleon for Mediawiki). How can I make it a proper style recognized by the extension? I tried adding it as a choice from the LocalSettings paremeter for style but I can't figure out how bridge the 'ext.headertabs.bootstrap' value and the right stylesheet. Lalquier (talk) 21:31, 10 March 2022 (UTC)

html entities no long render in tabs

I just upgraded Header Tabs to v2.2 (master) and overall its great, but I did notice the we lost the ability to use html entities (like &#128221) in the header tabs. The older versions allowed for it. Was support for html entities dropped by design or was that an undocumented feature that got eliminated unintentionally?

Thanks!

/Rich Revansx (talk) 23:47, 4 July 2022 (UTC)

images no longer usable as link text in #switchtablink

I just upgraded Header Tabs to v2.2 (master) and overall its great, but I did notice the we lost the ability to use images as the link text in the #switchtablink parser function. The older versions allowed for it. Was this capability dropped by design or was that an undocumented feature that got lost unintentionally?

Thanks!

/Rich Revansx (talk) 23:54, 4 July 2022 (UTC)

It's the latter. Yaron Koren (talk) 15:09, 5 July 2022 (UTC)

Error message after update to MW 1.39

After the update of MediaWiki to 1.39 there is a error message on all pages using Header Tabs. I am using the last version of Header Tabs.

The error message is:

Deprecated: Use of ParserOutput::addModules with non-array argument was deprecated in MediaWiki 1.38. [Called from HeaderTabs::tag in (...) .../HeaderTabs/indludes/HeaderTabs.php at line 26] in (...) .../includes/debug/MWDebug.php on line 381

What I am doing wrong? Could anyone help me to find the problem? Thanks! Ahaemmerli (talk) 12:24, 15 December 2022 (UTC)

Sorry about that - this was a real bug in Header Tabs. I just checked in a fix for this, so if you get the latest Header Tabs code, the problem should go away. Yaron Koren (talk) 18:21, 29 December 2022 (UTC)

$wgHeaderTabsDisableDefaultToc

Default "true" does not work for me. I still see the default ToC in version 2.2.2 on MW 1.39 when header tabs are used on the page. [[kgh]] (talk) 18:34, 9 January 2024 (UTC)

OO.ui error with MW1.42.3 and recent extensions

Hi. I m rebuilding a wiki from scratch with recent versions of everything. I currently have MW1.42.3 as a base, with the latest SMW and Page Forms, and now looking at installing Headertabs for compatibility with imported pages. The 1.42 branch of Headertabs is giving me this error. Any idea what could be causing it? I didn't see any particular requirements on the page.

Uncaught Error: Widget not found
    at mw.loader.impl.OO.ui.Element.static.unsafeInfuse (oojs-ui-core.js:741:9)
    at mw.loader.impl.OO.ui.Element.static.infuse (oojs-ui-core.js:709:35)
    at mw.loader.impl.OO.ui.infuse (oojs-ui-core.js:336:30)
    at HTMLDocument.eval (ext.headertabs.core.js:30:20)
    at mightThrow (jquery.js:3489:29)
    at jquery.js:3557:12

Lalquier (talk) 20:14, 27 October 2024 (UTC)

That error message doesn't look familiar, but I would definitely recommend using the master version of Header Tabs and not the REL1_42 version - as far as I know, the REL1_42 branch doesn't work with MW 1.42, because the fixes only came later. Yaron Koren (talk) 17:01, 29 October 2024 (UTC)

Thanks! Using the master version fixed that error. Lalquier (talk) 01:17, 30 October 2024 (UTC)

Great! Yaron Koren (talk) 13:41, 30 October 2024 (UTC)

Responsive header tabs

With MobileFrontend the tabs overflow the screen width for mobile devices. Is there a way to make this extension responsive so that the tabs stack vertically instead of overflow for mobile users? I'm using MW 1.40, HeaderTabs 2.2.185.64.143.45 18:18, 30 March 2025 (UTC)

I don't know of any way to do that, unfortunately... there is a plan to convert Header Tabs from using OOUI to Codex (the old and new JavaScript libraries, respectively) to display its tabs, which may or may not help with this. Yaron Koren (talk) 14:46, 31 March 2025 (UTC)