Issue Bug Resolved

#111488FormEngine: tab scroller is missing for tabs loaded after page load

Benjamin Kott 11/18/26, 10:14 updated 11/19/26, 09:15

Description

Problem

FormEngine tab bars (.nav-tabs) get the <typo3-backend-tab-scroller> only from a JavaScript wrap that runs once when the document is ready. Tabs that FormEngine loads later get no scroller: no start/end arrows, no scrolling of the active tab into view, and on narrow viewports the tabs overflow their container. This happens for an inline (IRRE) child with tabs that is expanded and loads its fields via AJAX, and for a new inline child added with “Create new”.

The scroller also creates its scroll buttons again whenever it is moved in the DOM, e.g. when inline records are sorted, which duplicates them.

Steps to reproduce

  1. Install EXT:styleguide and create the TCA demo data
  2. Edit a record of “inline 1n” (tx_styleguide_inline_1n) whose children are collapsed
  3. Expand a child, which has the tabs “General” and “meta”
  4. Inspect the child’s tab bar: its .nav-tabs sits directly in a div, not in typo3-backend-tab-scroller; make the window narrow and the tabs overflow the panel without scroll arrows

Cause

The tabs partial EXT:backend/Resources/Private/Partials/ModuleTemplate/Tabs.fluid.html, which FormEngine renders through AbstractContainer::renderTabMenu(), outputs a bare .nav-tabs. Build/Sources/TypeScript/backend/tab.ts wraps tab bars only in a single DocumentService.ready() callback. TabScrollerElement::createButtons() runs on every connect.

Suggested fix: render <typo3-backend-tab-scroller> around the .nav-tabs in the tabs partial, so later loaded FormEngine markup brings its scroller along, and create the scroll buttons only once per element.

Reviews 2

History 14

  1. Benjamin Kott commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-11-19T09:15:15+00:00" > 11/19/26, 09:15 </span>

    Applied in changeset commit:fb5851d6957278def84549516196fa730b33a421.