Angular Tabs, Pills & Accordion | ng-hub-ui-panels
Angular Content-Panels-Komponente, die sich als Tabs, Pills oder Accordion rendert, mit Routing, Reactive Forms, Tastaturnavigation und CSS-Variablen.
Zuletzt aktualisiert 16.09.2026
Übersicht
Warum Teams nach dieser Bibliothek suchen
Nutze diese Angular Panels-Komponente, wenn du Tabs-, Pills- und Accordion-Muster aus einer einzigen API benötigst, mit gerouteten Panels, Reactive-Forms-Bindung, Tastaturnavigation und Theming über CSS-Variablen.
Installieren
npm install ng-hub-ui-panelsSpringen zu
Ideal für
- Einstellungsseiten
- Produktdetail-Tabs
- FAQ-Accordions
- Dashboard-Bereiche
Über panels
ng-hub-ui-panels vereint Tabs, Pills und Accordion in einer einzigen standalone Angular-Komponente, die auf Signals aufbaut. Sie unterstützt geroutete Panels, Formularbindung per ControlValueAccessor, scrollbare und vertikale Leisten sowie vollständiges --hub-panels-*-Theming. Sie löst ng-hub-ui-accordion ab, dessen Accordion-Ansicht sie ersetzt, während sie den Token-Vertrag --hub-accordion-* beibehält.
Funktionsleitfäden
Visualisierungen
Eine Komponente, vier Ansichten: klassische unterstrichene Tabs, abgerundete Pills, gestapelte Accordion-Disclosure-Panels und rahmenlose, stets sichtbare Cards — umschaltbar über einen einzigen `type`-Input.
Beispiele:
Grundlegende Tabs
Grundlegende Tabs
Pills
Pills
Accordion-Ansicht
Accordion-Ansicht
Karten & Inhalts-Slots
Karten & Inhalts-Slots
hubPanelHeader / hubPanelFooter slots work in tabs, pills and accordion too. A single standalone <hub-panel> (no container):
hub-panel renders as a card by itself. Karten-Slots (variant, flush, fill)
Karten-Slots (variant, flush, fill)
Row 1 — the body scrolls; the header stays put.
Row 2 — the body scrolls; the header stays put.
Row 3 — the body scrolls; the header stays put.
Row 4 — the body scrolls; the header stays put.
Row 5 — the body scrolls; the header stays put.
Row 6 — the body scrolls; the header stays put.
Row 7 — the body scrolls; the header stays put.
Row 8 — the body scrolls; the header stays put.
Row 9 — the body scrolls; the header stays put.
Row 10 — the body scrolls; the header stays put.
Row 11 — the body scrolls; the header stays put.
Row 12 — the body scrolls; the header stays put.
Row 13 — the body scrolls; the header stays put.
Row 14 — the body scrolls; the header stays put.
Row 15 — the body scrolls; the header stays put.
Row 16 — the body scrolls; the header stays put.
Row 17 — the body scrolls; the header stays put.
Row 18 — the body scrolls; the header stays put.
Row 19 — the body scrolls; the header stays put.
Row 20 — the body scrolls; the header stays put.
Semantische Hinweise
Semantische Hinweise
An alert can use the same header/footer slots as a card:
Semantischer Leisten-Akzent
Semantischer Leisten-Akzent
Tab nav (inhaltslose Leiste)
Tab nav (inhaltslose Leiste)
Overview
The tab strip owns no content — this view is rendered by the host from active().
Selected value: overview
Strip-Layout
Layouten Sie den Header-Strip passend für jede Shell: stapeln Sie ihn vertikal neben dem Inhalt, strecken Sie die Header über die gesamte Breite oder machen Sie einen überlaufenden Strip scrollbar.
Beispiele:
Vertikale Tabs
Vertikale Tabs
Ausgerichtete Tabs
Ausgerichtete Tabs
Scrollbare Tabs
Scrollbare Tabs
Panel-Verwaltung
Deaktivieren Sie einzelne Panels und lassen Sie Benutzer Panels spontan über die ✕-Schaltfläche und die Delete-Taste hinzufügen oder entfernen.
Beispiele:
Deaktivierte Panels
Deaktivierte Panels
Entfernbare & dynamische Panels
Entfernbare & dynamische Panels
Benutzerdefinierte Templates
Ersetzen Sie den Klartext-Header durch ein beliebiges Angular-Template — Icons, Badges oder interaktive Steuerelemente — über die `hubPanelHeading`-Direktive.
Beispiele:
Benutzerdefinierte Überschriftsvorlagen
Benutzerdefinierte Überschriftsvorlagen
Zeilenaktionen im Accordion
Zeilenaktionen im Accordion
Formularintegration
Erstklassige ControlValueAccessor-Unterstützung bindet das/die aktive(n) Panel(s) an die reaktiven und template-getriebenen Formulare von Angular.
Beispiele:
Integration reaktiver Formulare
Integration reaktiver Formulare
Mehrfachauswahl
Mit `multiple` können mehrere Panels gleichzeitig geöffnet sein. In der Accordion-Ansicht werden sie alle erweitert; in den Tabs-/Pills-Ansichten startet jeder aktive Header sein eigenes sichtbares Panel, während die folgenden inaktiven Header oberhalb dieses Panels gruppiert bleiben, bis der nächste aktive Header einen neuen Block beginnt.
Beispiele:
Mehrfachauswahl
Mehrfachauswahl
Click an inactive tab to split the layout into a new panel block. Click an active tab to merge that block back.
Mehrere vertikale Kopfzeilen
Mehrere vertikale Kopfzeilen
Each active header starts a new row-like vertical block. The blocks stack top-to-bottom, and the whole layout scrolls horizontally only when one row needs more width.
Tabs
Pills
Accordion-Optionen
Die Accordion-Ansicht unterstützt mehrere gleichzeitig erweiterte Panels und ein randloses `flush`-Layout ohne äußeres Chrome.
Beispiele:
Akkordeon Mehrfach & Flush
Akkordeon Mehrfach & Flush
Barrierefreiheit
Vollständige Tastaturnavigation (Pfeile, Home, End, Delete), Roving-Tabindex und korrekte ARIA-Rollen für die tablist- und Accordion-Disclosure-Muster.
Beispiele:
Tastaturnavigation
Tastaturnavigation
Focus a tab, then use ← → Home End. Press Delete on a removable tab to close it.
Seitenpanel
Ein nicht-modales Panel, das an einer Kante seines Containers andockt: Es verschmälert den Inhalt (side) oder schwebt über dessen Rand (over) – ohne Backdrop, Scroll-Sperre oder Fokusfalle, sodass die Seite benutzbar bleibt, solange es geöffnet ist.
Beispiele:
Seitenpanel (nicht-modaler Begleiter)
Seitenpanel (nicht-modaler Begleiter)
sideInvoice draft
The page stays usable while the assistant is open: edit the field, scroll, select text.
Consulting — 8 h × €60.00
Design review — 3 h × €75.00
Hosting, September — €19.00
Domain renewal — €12.00
Support plan — €45.00
Travel — €38.50
Training session — 2 h × €60.00
Licence, annual — €240.00
Hi! Ask me to fill in any field of this invoice.
Hauptfunktionen
Letzte Änderungen
Version 22.12.1 - 9/16/26, 12:00 AM
changed: Repository, issue and README links follow the move to the hub-env organization. Issues for every Hub UI package are now gathered in hub-env/hub-ui, and the repository and bugs fields of the manifest point at the new addresses. No code, types or styles change.
Version 22.12.0 - 9/13/26, 12:00 AM
added: <hub-side-panel> inside a <hub-side-panel-container>: a side panel that is not a dialog. No backdrop, no scroll lock and no focus trap, so the page stays usable while it is open. mode="side" docks it and narrows the content; mode="over" floats it over the content edge, and a side panel falls back to over when the container is narrower than breakpoint (768 by default). Logical start/end position, a two-way open model, Escape to close, opt-in autoFocus with focus handed back on close, and content that survives closing. Themed through twelve --hub-side-panel-* tokens.
Version 22.11.0 - 9/8/26, 12:00 AM
changed: BREAKING — the seven exported classes are renamed with the Hub prefix: PanelsComponent, PanelComponent, PanelsConfig, PanelHeadingDirective, PanelHeadingActionsDirective, PanelHeaderDirective and PanelFooterDirective become HubPanelsComponent, HubPanelComponent, HubPanelsConfig, HubPanelHeadingDirective, HubPanelHeadingActionsDirective, HubPanelHeaderDirective and HubPanelFooterDirective. PanelComponent is an ordinary name for an ordinary thing, and an application that has a panel of its own will reach for it — an unprefixed export puts the library inside the consumer’s namespace and leaves them aliasing their way out of a collision they did not create. The selectors and the exported types were already prefixed, so the classes were the last part of this surface still spelled the other way. All seven old names stay exported as deprecated aliases resolving to the same classes, so imports, viewChild() lookups and a { provide: PanelsConfig, ... } provider all keep working, and they are removed in 23.0.0. See BREAKING_CHANGES.md.
fixed: Both READMEs name the classes that ship. The import block and every reference to the container, the panel and the config token still used the old names, so a reader copying the documented import wrote code compiling only against the deprecated aliases — which is exactly the audience this rename exists to move.
Version 22.10.4 - 9/6/26, 12:00 AM
added: A BREAKING_CHANGES.md file, written up with the three breaks this library had already shipped without one. The major number states which Angular major is targeted, so it can never be raised to warn of a break, which leaves this file as the only warning a consumer gets, and until now panels had nowhere to give it. It covers the two CSS breaks of 22.8.2 (the disclosure button stopped painting the row surface and stopped being position: relative, both filed as Changed and both released under a patch number) and the 22.3.0 scoping of the PanelsComponent injection to host: true, which stops a wrapper component's own <hub-panel> from joining a group outside its template. Each entry carries the migration the changelog only stated in passing. Documentation only: no code, types or styles change.
fixed: HubPanelAppearance and HubPanelVariant are now re-exported from the package entry point. The 21.3.0 notes announced them as exported types, but the barrel never listed them, so the union behind <hub-panel [appearance]> and [variant] was unreachable from outside the library: consumers had to redeclare it by hand in every project, or widen it to string and lose the very check the types exist for. No runtime change, the surface is type-only.
Version 22.10.3 - 9/1/26, 12:00 AM
changed: The homepage in the manifest points at this library's own documentation page rather than at the site root. It is the link a registry shows beside the package and the one a reader clicks from it, and landing on a front page they then have to search is a worse answer than landing on the reference for the package they were already looking at. Metadata only — no code, no types, no styles change, and nothing a consumer imports is affected.
Version 22.10.2 - 8/17/26, 12:00 AM
fixed: The published package declared no licence. An absent license field is not neutral — a registry reports it as unlicensed, which legally reads as all rights reserved, the most restrictive state possible rather than the most open. The intent was always MIT; it is now stated in package.json and carried in a LICENSE file that ships with the package.
Version 22.10.1 - 8/8/26, 12:00 AM
fixed: Documentation links now point at the canonical localized URLs. The README linked to https://hubui.dev/<path> with no locale prefix and no trailing slash, and both forms are 301-redirected, so every reader arriving from npm or GitHub landed on a redirect instead of the canonical page.
Version 22.10.0 - 7/28/26, 12:00 AM
changed: Accent resolution now imports the canonical resolveHubAccent from ng-hub-ui-utils; the private in-library copy was deleted. Behaviour is identical.
added: New required peer dependency: ng-hub-ui-utils >=22.7.0 (home of resolveHubAccent). ng add ng-hub-ui installs it automatically; manual installs need npm i ng-hub-ui-utils.
Version 22.9.0 - 7/28/26, 12:00 AM
added: New removeLabel input on <hub-panel> (default "Remove panel"): the accessible name announced for the ✕ remove button, overridable per panel so consumers can localize it.
fixed: The ✕ remove control was an aria-hidden <span> nested inside the tab / disclosure <button> — unfocusable, unannounced and unreachable by keyboard. It is now a real <button type="button"> with an aria-label, rendered as a SIBLING of the header control (the slot pattern hubPanelHeadingActions introduced): beside the tab button in the strip views, inside the accordion actions area at the row end. Clicking it still removes without toggling or selecting, it is disabled with its panel, and the .hub-panels__remove-btn class and its opacity tokens are unchanged.
fixed: Removing a panel through the ✕ now returns keyboard focus to the closest remaining header (as the Delete key already did) instead of dropping it on <body>. New public removePanelAndRefocus(panel) method on PanelsComponent, shared by the Delete-key handlers.
Version 22.8.3 - 7/26/26, 12:00 AM
fixed: Declared the real ng-hub-ui-ds peer range (>=22.0.0); the previous >=1.0.0 floor predates the --hub-ref-*/--hub-sys-* token architecture.
Version 22.8.2 - 7/9/26, 12:00 AM
fixed: The hairline closing an expanded accordion row stopped short of the row's end. It was an inset box-shadow on the disclosure button, which stopped spanning the whole header when 22.8.0 made it flex: 1 1 auto to free space for hubPanelHeadingActions. It is now drawn on .hub-panels__accordion-header--expanded, which always spans the full row.
fixed: togglePosition="end" put the chevron at the end of the BUTTON rather than of the row, so with hubPanelHeadingActions it landed between the heading and the affordances. The trailing chevron is now anchored to the header’s inline end, and whatever sits last in the row reserves its gutter through the new --hub-panels-accordion-toggle-gutter property.
changed: BREAKING (CSS contract): .hub-panels__accordion-btn no longer paints the row surface — it is transparent and the header’s surface shows through, which is what lets the inset hairline reach the row’s end. The --hub-panels-accordion-btn-bg and --hub-panels-accordion-active-bg tokens still drive the colour, now read by the header. A consumer who set background directly on .hub-panels__accordion-btn must move it to .hub-panels__accordion-header. See BREAKING_CHANGES.md.
changed: BREAKING (CSS contract): .hub-panels__accordion-btn is no longer position: relative; the header carries it instead, so the trailing chevron can be anchored to the row. A consumer who relied on the button as the containing block for absolutely positioned heading content must now give that content its own containing block. See BREAKING_CHANGES.md.
Version 22.8.1 - 7/9/26, 12:00 AM
fixed: togglePosition leaked into a nested accordion: the chevron side was a class on the container plus a descendant selector, so an accordion nested inside a panel body inherited the outer placement and could not choose its own. The flag now rides each <hub-panel> and the rule is scoped to that panel's own header.
Version 22.8.0 - 7/9/26, 12:00 AM
added: New hubPanelHeadingActions directive: a header-row slot for accordion affordances that must stay usable while the row is collapsed (edit, delete, a menu). It renders as a sibling of the disclosure button, so its controls are real controls, a click never toggles the panel and tab order follows the DOM. hubPanelHeading projects INSIDE that button (a nested <button> is invalid and unreachable by keyboard) and hubPanelHeader projects inside the collapse region (it vanishes when the row closes), so until now there was nowhere to put them.
added: New togglePosition input on <hub-panels> (start | end, default end; also on PanelsConfig): which side of the accordion header row the disclosure chevron sits on. Only the visual order moves — the DOM is untouched — and the offsets are logical, so start is the left edge in LTR and the right edge in RTL. Replaces the ::ng-deep order/margin override consumers were writing by hand. Exports the HubPanelsTogglePosition type.
changed: .hub-panels__accordion-header is now a flex row carrying the row surface (with a new --expanded modifier), the disclosure button being its flex child, so the actions slot shares the background in both states. The button’s own background rules are unchanged.
fixed: RTL in the accordion header: the disclosure button used the physical text-align: left and its chevron margin-left: auto, so under dir="rtl" the label stayed left-aligned and the chevron pinned to the wrong edge. Both are logical now.
Version 22.7.0 - 7/8/26, 12:00 AM
added: New --hub-panels-tab-border-end-radius token: the radius of a vertical tab’s corners on the edge that meets the panel body. They used to be hardcoded to 0, so the active tab always docked flush into the panel. Defaults to 0 (no visual change); raise it to render fully-rounded, standalone rail items such as a routed settings/profile subnav.
Version 22.6.0 - 7/7/26, 12:00 AM
added: New hub-panels-theme(...) SCSS mixin: one-call token theming for <hub-panels>. $accent feeds the single --hub-panels-accent slot (the component derives the emphasis/subtle/on family), alongside the panel surface and the tab appearance. Every parameter is null-defaulted and additive; for any token not exposed, set the --hub-panels-* custom property directly.
changed: Packaging: the library now ships its SCSS at /styles, exposing hub-panels-theme as a first-class package entry (@use 'ng-hub-ui-panels/styles' as *;).
Version 22.5.0 - 7/7/26, 12:00 AM
changed: variant on <hub-panel> / <hub-panels> now accepts ANY colour: on top of the built-in semantic accents it takes a registered custom accent or a literal colour (#ff0000, rgb(...), oklch(...), a CSS named colour), resolved through the shared resolveHubAccent helper. The single accent slot derives the rest of the family, so built-in colours are unchanged.
changed: Internal: @HostBinding / @HostListener decorators replaced by the host metadata object (Angular style guide). No public API or behaviour change.
Version 22.4.0 - 7/5/26, 12:00 AM
added: New <hub-tab-nav> — a lightweight, content-less, value-bound tab strip (role=tablist) that emits the selected value via a two-way active model, for segmented controls / filter switches / manual tabs-with-external-content. Supports tabs/pills appearances, justified/vertical layouts and roving-tabindex keyboard nav.
added: Card panels now honour [variant]: a plain card reflects data-variant and tints its bg/text/border from a single inline accent (--hub-panels-card-accent) with the same open color-mix + ds-tint model as the alert. New --hub-panels-card-border-style (e.g. dashed empty-state cards).
added: New <hub-panel flush> input (zero card body padding) and <hub-panel fill> input (fill-height card with a scrolling body; the wrappers gain stable classes and --hub-panels-body-gap spaces stacked children).
added: New <hub-panel standalone> static attribute: opts a loose panel out of an ancestor tabs/pills/accordion group in the same template so it renders as a plain card (the case host: true cannot cover).
changed: --hub-panels-card-box-shadow and --hub-panels-panel-header-bg are now inheritable (default moved to the usage-site var() fallback) so an ancestor can set them; identical default, no visual change.
Version 22.3.0 - 7/2/26, 12:00 AM
fixed: A standalone <hub-panel> nested (transitively) inside a tab pane no longer registers as a hidden tab of the outer <hub-panels>: the group injection is now bounded with host: true, so a panel binds only to a group declared in the same template and renders as a card/alert otherwise. The providers: [{ provide: PanelsComponent, useValue: null }] workaround is no longer needed.
changed: Canonical accent-slot derivation: the group role family (emphasis/subtle/on) now derives locally from the single --hub-panels-accent slot with the design-system formulas, so custom accents re-derive the full family at runtime; built-in variants only re-base the accent slot.
changed: The alert open-set default (appearance="alert" with a custom variant) uses the same canonical tints as the built-ins (12% background over surface, 80% text over ink).
Version 22.2.0 - 6/26/26, 12:00 AM
added: Open-set accent variants: <hub-panels variant="…"> and <hub-panel appearance="alert" variant="…"> ship all 9 built-ins (primary…dark) with exact ds tints, and any custom string keeps working at runtime by defining a single --hub-sys-color-<name>.
Version 22.1.0 - 6/22/26, 12:00 AM
added: New variant input on <hub-panels> selecting the semantic accent of the navigation strip (active/hover tab, active pill, active accordion header). Built-in variants (primary | success | danger | warning | info) use the exact design-system tints; any custom string is also accepted and derived with color-mix. Defaults to primary.
added: New group-accent tokens --hub-panels-accent, --hub-panels-accent-emphasis and --hub-panels-accent-subtle; the strip active/hover affordances now resolve through this single accent instead of being hard-wired to --hub-sys-color-primary*.
changed: The outer container chrome now inherits from the --hub-container-* base layer (re-base hook), so overriding a container token on a subtree re-bases the panels chrome. No visual change with default tokens.
Version 22.1.1 - 6/25/26, 12:00 AM
fixed: Design-token consistency pass: inline fallback defaults now match the canonical ng-hub-ui-ds values, and the hardcoded literals left behind (z-index, font-weight, line-height, radii and theme-aware colours) go through their --hub-sys-* / --hub-ref-* tokens, so they follow the active theme. No visual change when the ds tokens are loaded.
Version 22.0.0 - 6/17/26, 12:00 AM
changed: Aligned with Angular 22. The major number of this package states the Angular major it targets, so this release is a compatibility statement rather than an API break.
changed: README documentation standardized.
Version 21.3.0 - 6/16/26, 12:00 AM
added: New alert appearance for a standalone <hub-panel>: appearance="alert" with a variant renders a semantic callout (role="alert").
added: New variant input (primary | success | danger | warning | info) selecting the alert colour; omit it for a neutral alert. Exported HubPanelAppearance and HubPanelVariant types.
added: New alert tokens (--hub-panels-alert-*); each variant re-points them at the --hub-sys-color-<variant>-{subtle,border-subtle,emphasis} family, so the alert inherits every theme and dark mode automatically.
Version 21.2.0 - 6/14/26, 12:00 AM
added: New card visualization (type="card"): a chromeless format with no navigation strip where every <hub-panel> is always visible and styled as a card.
added: A <hub-panel> can now be used standalone, outside any <hub-panels> container, rendering as a card on its own.
added: New content-slot directives hubPanelHeader and hubPanelFooter, rendering header/footer bands in every view, distinct from the navigational hubPanelHeading.
Version 21.1.1 - 6/12/26, 12:00 AM
added: New token: --hub-panels-header-bg, used by the tabs/pills strip background while defaulting to the panel surface.
added: New token: --hub-panels-pill-content-border-width, which controls the bordered card chrome in the pills content area.
changed: The active header background now defaults to --hub-panels-content-bg so the active tab/panel fusion stays aligned when themes retint the content surface.
changed: The pills content area is borderless by default; themes can opt back into a bordered card by overriding --hub-panels-pill-content-border-width.
Version 21.1.0 - 6/11/26, 12:00 AM
added: Multiple selection in the tabs/pills views: each open pane becomes its own bordered box placed next to the others (side by side when horizontal, stacked when vertical), with a per-pane minimum and scroll on overflow.
added: New tokens: --hub-panels-pane-min-width, --hub-panels-pane-min-height, --hub-panels-pane-gap, --hub-panels-nav-content-gap, --hub-panels-pill-gap.
fixed: Accordion content was always empty (two unselected ng-content slots); replaced with a single projection slot.
fixed: tabs and vertical tabs now render as a single bordered box around the strip and content together (not two boxes); pills gain spacing before a bordered content card.
changed: Smooth strip scrolling, not-allowed cursor on disabled headers, and full-width container.
Version 21.0.0 - 6/11/26, 12:00 AM
added: Initial release of ng-hub-ui-panels with tabs, pills and accordion visualizations.
added: ControlValueAccessor integration with single and multiple selection, bindValue and compareWith.
added: Routed panels via routerLink with route/full pathMatch and a <router-outlet> content area.
added: Keyboard navigation (arrows/Home/End/Delete), scrollable, vertical and justified strips.
added: Accordion view with multiple expansion, flush layout and an animated grid-based collapse.
added: Custom header templates through the hubPanelHeading directive and full --hub-panels-* theming.
changed: Supersedes ng-hub-ui-accordion; the accordion view honours the --hub-accordion-* token contract for theme compatibility.
Verwandte Bibliotheken
Häufig gestellte Fragen
Wie baue ich Tabs, Pills oder ein Accordion in Angular mit einer einzigen Komponente?
Importieren Sie HubPanelsComponent und HubPanelComponent und schreiben Sie <hub-panels type="accordion"> mit einem <hub-panel heading="…"> pro Abschnitt. type nimmt tabs, pills, accordion oder card, und ein Wechsel tauscht das ganze Muster aus, ohne dass Sie das Markup anfassen. multiple lässt im Accordion-Modus mehr als einen Abschnitt offen, vertical stellt den Streifen hochkant, scrollable hält einen langen Streifen auf einer Zeile, und panelChange sagt Ihnen, welches Panel aktiv geworden ist.
Kann ein Panel dem Router folgen oder an ein Reactive Form gebunden werden?
Beides. Geben Sie einem Panel ein routerLink, bei Bedarf mit queryParams und pathMatch, und der Inhaltsbereich wird zu einem Router-Outlet, das der URL folgt. Der Container implementiert ControlValueAccessor, <hub-panels formControlName="section"> bindet das aktive Panel also an ein Form Control; bindValue bestimmt, welche Eigenschaft als Wert weitergereicht wird, und compareWith entscheidet über die Identität. An einem einzelnen Panel ist active ein model(), für den einfachen Fall funktioniert also [(active)].
Sind die Tabs und das Accordion per Tastatur bedienbar?
Ja, und die Rollen sind echt: role=tablist und role=tab mit wanderndem tabindex und aria-selected, jedes Panel ein tabpanel, das von seinem Tab beschriftet wird. Die Pfeiltasten bewegen sich zwischen den Panels — hoch und runter nur, wenn vertical gesetzt ist —, Home und Ende springen an die Enden, und Entf entfernt ein als removable markiertes Panel und setzt den Fokus auf das nächste. Im Accordion-Modus ist jede Überschrift ein natives button mit aria-expanded, und ein eingeklappter Bereich ist inert statt nur versteckt, nichts darin nimmt also den Fokus.
Ist ng-hub-ui-panels ein direkter Ersatz für ng-hub-ui-accordion?
Für die Accordion-Ansicht ja: aus <hub-accordion> wird <hub-panels type="accordion">, aus <hub-accordion-panel title> wird <hub-panel heading>, und jede --hub-accordion-*-Variable, die Sie bereits gesetzt haben, gilt weiterhin, denn jedes Accordion-Token liest sie, bevor es auf seinen Rückfallwert geht. Zwei Bedingungen hängen daran. Diese Variablen erreichen nur die Accordion-Ansicht, nicht Tabs, Pills oder Cards. Und panels verlangt Angular 21, ng-hub-ui-utils und @angular/router, den es injiziert, ob Sie ein geroutetes Panel verwenden oder nicht — eine Anwendung ohne provideRouter scheitert also beim Erzeugen der Komponente.