Place TabPanel directly inside Tabs and set its required tabId to the matching item id. Its projected content is rendered only while that tab is active. It is not an independent visibility container. Use the parent Tabs for activeId, label Templates and selection events.
These inputs require a model or function, not a checkbox. Edit the same-named field in the Source component and bind it in the template; data already used by this preview appears in the state above.
tabId ยท K
In Source: define tabId with this type and use [tabId]="tabId" (or tabId() for a signal).
The parent links the selected tab to its panel through generated IDs. Keep a panel for every tab, including disabled items. Put form controls and actions in the panel, not inside the tab button.
Key
Action
Tab
Follow the normal focus order of links, fields and actions inside the content; the container adds no roving-focus model.
Enter
Activate a focused native button or follow a focused link inside the content.
Space
Activate a focused native button inside the content; fields keep normal text editing.
Inputs and Outputs match the pinned Core package. Named types link to their definitions. Templates include executable examples for each supported region.
Inputs
Configure the component with [property]="value". Your application supplies these values; the component does not replace the state you pass in.
Name
Type
Default
Template binding
Description
tabId
K
Required
[tabId]
Required key matching an item in the parent Tabs.
Templates
ng-content projects content into the component. TemplateRef inputs receive a template; ng-template directives identify templates with a typed context. A directive shared by an entrypoint is not necessarily a slot of this component.