Solvedpolaris react Tabs Documentation

Can you please extend Tabs documentation? It's really confusing how it works and the example doesn't really help. Do Tabs run their own state or I have to implement it for the selected tab. How are children managed, how do I set the content for a tab? What do the properties of tabs mean? I understand Title but id and panelID?

10 Answers

✔️Accepted Answer

Hi @AdityaAnand1. Like @lemonmade said above, this isn't automatic, and the state needs to be managed from within your app. This is an example of a simple component that manages state for a set of tabs.

import React, { Component } from 'react';

import {Tabs} from '@shopify/polaris';

import '@shopify/polaris/styles.css';

class App extends Component {
  constructor(props) {

    this.handleTabChange = this.handleTabChange.bind(this);

    this.state = {
      selectedTab: 0,

  handleTabChange(selectedTab) {

  render() {
    const {selectedTab} = this.state;

    const tabs = [
        id: 'tab1',
        title: 'something1',
        panelID: 'panel2',
        id: 'tab2',
        title: 'something2',
        panelID: 'panel2',

    const tabPanels = [
        <Tabs.Panel id="panel1">
        <Tabs.Panel id="panel2">
          something else

    return (

export default App;

Hopefully this helps clarify how these can be used.

Other Answers:

Hi @nishikawa7863, I've added an issue to our internal tracker for improving the documentation here. Definitely agree that we have not documented this component particularly well. Here's some brief answers to your questions, though:

  1. Tabs do not manage their own state. You must provide the index of the selected tab as the selected prop, and we will tell you when the selected tab changes by giving you the new selected index as the only argument to the onSelect callback.

  2. You have two choices for children. The simpler way is to provide them as children of the Tabs component. If you go this way, you will need to decide what children to actually put in based on the selected tab (this is a little awkward but ends up being good for performance because you do not render a bunch of content for hidden tabs unnecessarily). The second way is to just use the selected tab state that you passed to tabs/ updated in onSelect, and then render something, somewhere on the page based on the selected tab. We often have to do this in cases where the tabs themselves are visually disconnected from the content then control.

  3. panelID is intended to connect a tab to a "panel" (container around the content that tab controls). This is useful for accessibility purposes as screen readers will associate the panel to the content. Essentially, you provide a panelID for the tab, and if you render the contents of that tab elsewhere on the page (that is, not as children of Tabs), you would wrap them in a Tabs.Panel component with an id that matches the panelID (though I just noted, we actually expose the panel as Tabs.panel — will add an issue to address this ASAP as well). This whole process happens automatically when you pass in the tab's contents as children of Tabs

I will update this issue when we ship fixes for these issues.

Any progress on this by any chance? I'm trying to implement the simpler option from your #2 but struggling a bit. Any chance you can provide an example of that?

More Issues: