Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

@atlaskit/tabs

atlassian103.5kApache-2.018.1.4TypeScript support: included

Tabs are used to organize content by grouping similar information on the same page.

readme

Tabs

Tabs are used to organize content by grouping similar information on the same page.

Installation

yarn add @atlaskit/tabs

Usage

Detailed docs and example usage can be found here.

changelog

@atlaskit/tabs

18.1.4

Patch Changes

  • Updated dependencies

18.1.3

Patch Changes

  • #182316 3e3e11916be69 - Migrated the internal usage of @atlaskit/focus-ring which uses Emotion for styling, to the new version built with Compiled CSS-in-JS.

18.1.2

Patch Changes

  • Updated dependencies

18.1.1

Patch Changes

18.1.0

Minor Changes

  • #157071 a149a0b1559ec - We are testing the migration to the ADS Link component behind a feature flag. If this fix is successful it will be available in a later release.

Patch Changes

  • Updated dependencies

18.0.3

Patch Changes

  • #129972 b2d69a39e6687 - Update @compiled/react dependency for improved type checking support.
  • Updated dependencies

18.0.2

Patch Changes

18.0.1

Patch Changes

  • Updated dependencies

18.0.0

Major Changes

Patch Changes

  • Updated dependencies

17.3.0

Minor Changes

Patch Changes

  • Updated dependencies

17.2.4

Patch Changes

  • Updated dependencies

17.2.3

Patch Changes

  • Updated dependencies

17.2.2

Patch Changes

17.2.1

Patch Changes

  • Updated dependencies

17.2.0

Minor Changes

Patch Changes

  • Updated dependencies

17.1.0

Minor Changes

17.0.2

Patch Changes

17.0.1

Patch Changes

  • Updated dependencies

17.0.0

Major Changes

  • #168353 cbd859b752028 - Migrated from @emotion/react to @compiled/react in order to improve performance, align with the rest of the Atlaskit techstack, and support React 18 Streaming SSR.

    Please note, in order to use this version of @atlaskit/tabs, you will need to ensure that your bundler is configured to handle .css imports correctly. Most bundlers come with built-in support for .css imports, so you may not need to do anything. If you are using a different bundler, please refer to the documentation for that bundler to understand how to handle .css imports.

    For more information on the migration, please refer to RFC-73 Migrating our components to Compiled CSS-in-JS.

16.5.4

Patch Changes

  • Updated dependencies

16.5.3

Patch Changes

  • #165531 57f451bda8919 - Adds side-effect config to support Compiled css extraction in third-party apps

16.5.2

Patch Changes

  • Updated dependencies

16.5.1

Patch Changes

  • Updated dependencies

16.5.0

Minor Changes

16.4.2

Patch Changes

  • Updated dependencies

16.4.1

Patch Changes

  • Updated dependencies

16.4.0

Minor Changes

  • #127511 db30e29344013 - Widening range of react and react-dom peer dependencies from ^16.8.0 || ^17.0.0 || ~18.2.0 to the wider range of ^16.8.0 || ^17.0.0 || ^18.0.0` (where applicable).

    This change has been done to enable usage of `react@18.3as well as to have a consistent peer dependency range forreactandreact-domfor/platform` packages.

Patch Changes

  • Updated dependencies

16.3.2

Patch Changes

  • Updated dependencies

16.3.1

Patch Changes

  • Updated dependencies

16.3.0

Minor Changes

16.2.4

Patch Changes

  • Updated dependencies

16.2.3

Patch Changes

  • Updated dependencies

16.2.2

Patch Changes

  • Updated dependencies

16.2.1

Patch Changes

  • Updated dependencies

16.2.0

Minor Changes

  • #111016 d131599730792 - Explicitly set jsxRuntime to classic via pragma comments in order to avoid issues where jsxRuntime is implicitly set to automatic.

Patch Changes

  • Updated dependencies

16.1.2

Patch Changes

  • Updated dependencies

16.1.1

Patch Changes

  • Updated dependencies

16.1.0

Minor Changes

16.0.0

Major Changes

15.0.0

Major Changes

  • #91586 e229d87eecd0 - - [ux] Removed horizontal padding from Tab container to ensure Tab labels and panel content align with other elements on the page. Tab label hit-boxes remain the same.
    • Adjusted line height and overall Tab label height to be consistent with the Atlassian Design System.

14.1.0

Minor Changes

14.0.5

Patch Changes

14.0.4

Patch Changes

  • Updated dependencies

14.0.3

Patch Changes

  • Updated dependencies

14.0.2

Patch Changes

  • Updated dependencies

14.0.1

Patch Changes

  • Updated dependencies

14.0.0

Major Changes

  • #41866 ed8b6957789 - Removes any usage of deprecated legacy theming APIs. These have been superseeded by design tokens.

13.4.9

Patch Changes

  • #40650 07aa588c8a4 - Reverts the fix to text descender cut-off, due to incompatibilities with Firefox and Safari.

13.4.8

Patch Changes

  • Updated dependencies

13.4.7

Patch Changes

13.4.6

Patch Changes

13.4.5

Patch Changes

  • #38753 e7f99a81404 - Update to use xcss where possible. There should be no difference in behaviour.
  • Updated dependencies

13.4.4

Patch Changes

  • #38209 56b444b56a8 - Fix a bug where text descenders were cut off at high zoom levels on Windows

13.4.3

Patch Changes

  • #35441 599bfe90ee3 - Internal change to use shape tokens. There is no expected visual change.

13.4.2

Patch Changes

13.4.1

Patch Changes

13.4.0

Minor Changes

Patch Changes

  • Updated dependencies

13.3.13

Patch Changes

13.3.12

Patch Changes

  • Updated dependencies

13.3.11

Patch Changes

  • Updated dependencies

13.3.10

Patch Changes

  • #27891 eadbf13d8c0 - Updated usages of Text, Box, Stack, and Inline primitives to reflect their updated APIs. There are no visual or behaviour changes.
  • Updated dependencies

13.3.9

Patch Changes

  • #28064 b0f6dd0bc35 - Updated to use typography tokens. There is no expected behaviour or visual change.

13.3.8

Patch Changes

  • Updated dependencies

13.3.7

Patch Changes

  • Updated dependencies

13.3.6

Patch Changes

  • Updated dependencies

13.3.5

Patch Changes

  • #25984 0637c50e226 - Updated Tabs compnent to prefer to use focus-visible over focus css selectors.

13.3.4

Patch Changes

  • #25860 e35fc41dc33 - Internal change to use updated primtive spacing prop values. No expected behaviour change.
  • Updated dependencies

13.3.3

Patch Changes

  • #26303 9827dcb82b8 - No-op change to introduce spacing tokens to design system components.

13.3.2

Patch Changes

  • #24710 0d42cd1c926 - Internal changes to the way styles are applied. There should be no noticeable changes to consumers.

13.3.1

Patch Changes

13.3.0

Minor Changes

  • #24004 7ec1c1a023f - Updates @emotion/core to @emotion/react; v10 to v11. There is no expected behavior change.

Patch Changes

  • Updated dependencies

13.2.13

Patch Changes

13.2.12

Patch Changes

13.2.11

Patch Changes

  • Updated dependencies

13.2.10

Patch Changes

13.2.9

Patch Changes

  • Updated dependencies

13.2.8

Patch Changes

  • #19618 62edf20ab1e - Migrates all usage of brand tokens to either selected or information tokens. This change is purely for semantic reasons, there are no visual or behavioural changes.
  • Updated dependencies

13.2.7

Patch Changes

  • Updated dependencies

13.2.6

Patch Changes

  • #16752 19d72473dfb - The no-unsafe-design-token-usage eslint rule now respects the new token naming conventions when auto-fixing by correctly formatting token ids.
  • Updated dependencies

13.2.5

Patch Changes

  • Updated dependencies

13.2.4

Patch Changes

  • #15998 f460cc7c411 - Builds for this package now pass through a tokens babel plugin, removing runtime invocations of the tokens() function and improving bundle size.
  • Updated dependencies

13.2.3

Patch Changes

  • Updated dependencies

13.2.2

Patch Changes

  • Updated dependencies

13.2.1

Patch Changes

  • Updated dependencies

13.2.0

Minor Changes

  • #13302 cc54bf994d6 - Instrumented Tabs with the new theming package, @atlaskit/tokens.

    New tokens will be visible only in applications configured to use the new Tokens API (currently in alpha). These changes are intended to be interoperable with the legacy theme implementation. Legacy dark mode users should expect no visual or breaking changes.

Patch Changes

  • af4bca32ad4 - Internal changes to supress eslint rules.
  • Updated dependencies

13.1.4

Patch Changes

13.1.3

Patch Changes

13.1.2

Patch Changes

  • #12328 ecbf4a3267f - [ux] Fix tabs focus ring in the windows high contrast mode
  • Updated dependencies

13.1.1

Patch Changes

13.1.0

Minor Changes

  • #10569 4f40ecb4471 - [ux] Added Home and End keys handlers for tablist. Changed arrow keys handlers to make tabs cycled. Now when you press the left arrow key on the first tab the last tab will be selected and when you press right arrow key on the last tab the first tab will be selected

Patch Changes

  • Updated dependencies

13.0.1

Patch Changes

  • Updated dependencies

13.0.0

Major Changes

  • #9756 c17fe6144f8 - ### Major Changes

    In this version, Tabs has had a pretty substantial rewrite. As well as now being dramatically faster and more lightweight, it has a brand new flexible composable API and a bunch of accessibility improvements.

    Composable API

    The old version of Tabs had a tabs prop that would map to TabItem's and TabContent's.

    import Tabs from '@atlaskit/tabs';

const ComponentUsingTabs = () => (
  <Tabs tabs={
    { label: 'Tab 1', content: 'One' },
    { label: 'Tab 2', content: 'Two' },
    { label: 'Tab 3', content: 'Three' },
  ]} />
);

    We've changed the language to match the W3 spec so a TabItem is now a Tab and a TabContent is a TabPanel. We now export these components as well as a TabList so consumers use a composable API that matches the DOM structure.

    import Tabs, { Tab, TabList, TabPanel } from '@atlaskit/tabs';

const ComponentUsingTabs = () => (
  <Tabs
    id="component-using-tabs"
  >
    <TabList>
      <Tab>Tab 1</Tab>
      <Tab>Tab 2</Tab>
      <Tab>Tab 3</Tab>
    </TabList>
    <TabPanel>
      One
    </TabPanel>
    <TabPanel>
      Two
    </TabPanel>
    <TabPanel>
      Three
    </TabPanel>
  </Tabs>
);

    This allows you to easily customise your usage, for example if you want to add a tooltip.

    import Tabs, { Tab, TabList, TabPanel } from '@atlaskit/tabs';
import Tooltip from '@atlaskit/tooltip';

const TooltipTab = ({ label, tooltip }: { label: string; tooltip: string }) => (
  <Tooltip content={tooltip}>
    <Tab>{label}</Tab>
  </Tooltip>
);

const ComponentUsingTabs = () => (
  <Tabs
    id="component-using-tabs"
  >
    <TabList>
      <TooltipTab label="Tab 1" tooltip="Tooltip for tab 1" />
      <TooltipTab label="Tab 2" tooltip="Tooltip for tab 2" />
      <TooltipTab label="Tab 3" tooltip="Tooltip for tab 3" />
    </TabList>
    <TabPanel>
      One
    </TabPanel>
    <TabPanel>
      Two
    </TabPanel>
    <TabPanel>
      Three
    </TabPanel>
  </Tabs>
);

    Hooks replacing Component prop

    The component prop allowed you to customise the Tab and TabPanel. This approach seemed counter-intuitive and had a performance impact regardless of whether you were using it. Instead with composability we have have added two hooks, useTab and useTabPanel.

    To create a custom Tab, call useTab and spread those attributes onto the custom tab. From there you can use it in place of a Tab. For example if you want to change the font size you would do so like this.

    import { useTab } from '@atlaskit/tabs';

const CustomTab = ({ label }: { label: string }) => {
  const tabAttributes = useTab();

  return (
    <div
      css={css`
        font-size: 16px;
      `}
      {...tabAttributes}
    >
      {label}
    </div>
  );
};

    Likewise, to create a custom TabPanel, call useTabPanel and spread those attributes onto the custom tab panel.

    import { useTabPanel } from '@atlaskit/tabs';

const CustomTabPanel = ({ body }: { body: string }) => {
  const tabPanelAttributes = useTabPanel();

  return (
    <div
      css={css`
        margin: 12px;
      `}
      {...tabPanelAttributes}
    >
      {body}
    </div>
  );
};

    onSelect -> onChange

    The onSelect prop has been renamed to onChange to be consistent with other design system components. Internal state has now changed to keep track of the selected index. Previously the object in the tabs prop array of type TabData was passed as well as the index. If you were using this object you will have to change to use the index.

    The type has changed from (selected: TabData, selectedIndex: number, analyticsEvent: UIAnalyticsEvent) => void; to (index: number, analyticsEvent: UIAnalyticsEvent) => void;

    This also means if you are using the selected prop you will have to ensure you are using the index of the selected tab instead of the object of type TabData.

    isSelectedTest

    Previously you could provide the prop isSelectedTest to Tabs and it would determine what tab is selected by seeing what tab returns true when isSelectedTest is called. This is a messy API that effectively means there were two ways of making Tabs controlled. If you are using isSelectedTest you should swap to using the selected prop to indicate that a tab is selected.

    Accessibility and required ID

    According to the w3 spec each tab should be linked to its corresponding tab panel. We have added the aria-controls attribute to tabs and the aria-labelledby attribute to tab panels. In order to do this we needed to generate a unique id for each tab and tab panel. To ensure these id's are unique if there are multiple Tabs components on the same page there is now a required id prop.

    shouldUnmountTabPanelOnChange

    There was previously a prop isContentPersisted which defaults to false. When true it would render all tab panels. The new default behaviour of Tabs is to leave each tab panel mounted on the page after it has been selected. This means that tab panels will only mount if selected and will not unmount and remount when changing tabs. In light of this change, isContentPersisted has been removed and shouldUnmountTabPanelOnChange has been introduced. It defaults to false and if it is set to true it will unmount a TabPanel when it is not selected. Effectively shouldUnmountTabPanelOnChange is the inverse of isContentPersisted.

    Other changes

    • Remove TabItem and TabContent export.
    • Remove the types: TabItemElementProps, TabItemComponentProvided, TabContentComponentProvided, TabItemType, TabContentType, SelectedProp, IsSelectedTestFunction, OnSelectCallback, TabsState, TabsNavigationProps and Mode.

Patch Changes

  • 4a969d5c40f - Fix a bug where the active element is blurred instead of the current element when clicked.
  • 1adf9a493f5 - Fix codemod issue
  • Updated dependencies

12.1.3

Patch Changes

  • #8644 79c23df6340 - Use injected package name and version for analytics instead of version.json.

12.1.2

Patch Changes

  • #6930 e795d0a849 - The Tabs component now uses emotion instead of styled-components for it's internal styling.

12.1.1

Patch Changes

12.1.0

Minor Changes

  • #6228 98c957d889 - [ux] Content of tabs will be preserved on the DOM while switching between tabs

12.0.6

Patch Changes

  • #5497 5f58283e1f - Export types using Typescript's new "export type" syntax to satisfy Typescript's --isolatedModules compiler option. This requires version 3.8 of Typescript, read more about how we handle Typescript versions here: https://atlaskit.atlassian.com/get-started Also add typescript to devDependencies to denote version that the package was built with.

12.0.5

Patch Changes

  • Updated dependencies

12.0.4

Patch Changes

12.0.3

Patch Changes

  • #3885 6c525a8229 - Upgraded to TypeScript 3.9.6 and tslib to 2.0.0

    Since tslib is a dependency for all our packages we recommend that products also follow this tslib upgrade to prevent duplicates of tslib being bundled.

12.0.2

Patch Changes

  • #3293 954cc87b62 - The readme and package information has been updated to point to the new design system website.

12.0.1

Patch Changes

12.0.0

Major Changes

Patch Changes

  • Updated dependencies

11.2.11

Patch Changes

  • #2866 54a9514fcf - Build and supporting files will no longer be published to npm

11.2.10

Patch Changes

11.2.9

Patch Changes

  • Updated dependencies

11.2.8

Patch Changes

11.2.7

Patch Changes

11.2.6

Patch Changes

11.2.5

Patch Changes

11.2.4

Patch Changes

11.2.3

Patch Changes

  • [patch]36f6e99c5b:

    Fix type errors caused when generating declaration files

11.2.2

Patch Changes

  • [patch]d222c2b987:

    Theme has been converted to Typescript. Typescript consumers will now get static type safety. Flow types are no longer provided.

    Breaking

    ** getTokens props changes ** When defining the value function passed into a ThemeProvider, the getTokens parameter cannot be called without props; if no props are provided an empty object {} must be passed in:

    <CustomTheme.Provider
  value={t => ({ ...t(), backgroundColor: '#333'})}
>

    becomes:

    <CustomTheme.Provider
  value={t => ({ ...t({}), backgroundColor: '#333'})}
>

    ** Color palette changes ** Color palettes have been moved into their own file. Users will need to update imports from this:

    import { colors } from '@atlaskit/theme';

colors.colorPalette('8');

    to this:

    import { colorPalette } from '@atlaskit/theme';

colorPalette.colorPalette('8');

    or for multi entry-point users:

    import * as colors from '@atlaskit/theme/colors';

colors.colorPalette('8');

    to this:

    import * as colorPalettes from '@atlaskit/theme/color-palette';

colorPalettes.colorPalette('8');

11.2.1

Patch Changes

  • [patch]35d2229b2a:

    Adding missing license to packages and update to Copyright 2019 Atlassian Pty Ltd.

11.2.0

Minor Changes

  • [minor]99957d4a20:

    Adding an optional prop testId that will set the attribute value data-testid. It will help products to write better integration and end to end tests.

11.1.1

Patch Changes

  • [patch]a2d0043716:

    Updated version of analytics-next to fix potential incompatibilities with TS 3.6

11.1.0

Minor Changes

11.0.9

Patch Changes

  • [patch]097b696613:

    Components now depend on TS 3.6 internally, in order to fix an issue with TS resolving non-relative imports as relative imports

11.0.8

Patch Changes

11.0.7

Patch Changes

  • [patch]708028db86:

    Change all the imports to theme in Core to use multi entry points

11.0.6

Patch Changes

  • [patch]de35ce8c67:

    Updates component maintainers

11.0.5

Patch Changes

  • [patch]926b43142b:

    Analytics-next has been converted to Typescript. Typescript consumers will now get static type safety. Flow types are no longer provided. No behavioural changes.

    Breaking changes

    • withAnalyticsForSumTypeProps alias has been removed, please use withAnalyticsEvents
    • AnalyticsContextWrappedComp alias has been removed, please use withAnalyticsContext

    Breaking changes to TypeScript annotations

    • withAnalyticsEvents now infers proptypes automatically, consumers no longer need to provide props as a generic type.
    • withAnalyticsContext now infers proptypes automatically, consumers no longer need to provide props as a generic type.
    • Type WithAnalyticsEventProps has been renamed to WithAnalyticsEventsProps to match source code
    • Type CreateUIAnalyticsEventSignature has been renamed to CreateUIAnalyticsEvent to match source code
    • Type UIAnalyticsEventHandlerSignature has been renamed to UIAnalyticsEventHandler to match source code
    • Type AnalyticsEventsPayload has been renamed to AnalyticsEventPayload
    • Type ObjectType has been removed, please use Record<string, any> or [key: string]: any
    • Type UIAnalyticsEventInterface has been removed, please use UIAnalyticsEvent
    • Type AnalyticsEventInterface has been removed, please use AnalyticsEvent
    • Type CreateAndFireEventFunction removed and should now be inferred by TypeScript
    • Type AnalyticsEventUpdater removed and should now be inferred by TypeScript

11.0.4

Patch Changes

  • [patch]3342f64d5e:

    Removed unused dependencies from package.json for tabs: keycode was unused.

11.0.3

Patch Changes

  • [patch]f34776be97:

    Type definition files are now referenced in package.json

11.0.2

Patch Changes

  • [patch]9f8ab1084b:

    Consume analytics-next ts type definitions as an ambient declaration.

11.0.1

Patch Changes

  • [patch]d0db01b410:

    TypeScript users of withAnalyticsEvents and withAnalyticsContext are now required to provide props as a generic type. This is so that TypeScript can correctly calculate the props and defaultProps of the returned component.

    Before:

    withAnalyticsEvents()(Button) as ComponentClass<Props>;

    After:

    withAnalyticsEvents<Props>()(Button);

11.0.0

Major Changes

  • [major]61a919319a:

    @atlaskit/tabs has been converted to Typescript. Typescript consumers will now get static type safety. Flow types are no longer provided. No API or behavioural changes. tabIndex now only accepts type number.

10.0.4

Patch Changes

  • [patch]4615439434:

    index.ts will now be ignored when publishing to npm

10.0.3

10.0.2

  • [patch]b0ef06c685:

    • This is just a safety release in case anything strange happened in in the previous one. See Pull Request #5942 for details

10.0.1

10.0.0

  • [major]7c17b35107:

    • Updates react and react-dom peer dependencies to react@^16.8.0 and react-dom@^16.8.0. To use this package, please ensure you use at least this version of react and react-dom.

9.0.1

9.0.0

  • [major]76299208e6:

    • Drop ES5 from all the flow modules

    Dropping CJS support in all @atlaskit packages

    As a breaking change, all @atlaskit packages will be dropping cjs distributions and will only distribute esm. This means all distributed code will be transpiled, but will still contain import and export declarations.

    The major reason for doing this is to allow us to support multiple entry points in packages, e.g:

    import colors from `@atlaskit/theme/colors`;

    Previously this was sort of possible for consumers by doing something like:

    import colors from `@atlaskit/theme/dist/esm/colors`;

    This has a couple of issues. 1, it treats the file system as API making internal refactors harder, we have to worry about how consumers might be using things that aren't actually supposed to be used. 2. We are unable to do this internally in @atlaskit packages. This leads to lots of packages bundling all of theme, just to use a single color, especially in situations where tree shaking fails.

    To support being able to use multiple entrypoints internally, we unfortunately cannot have multiple distributions as they would need to have very different imports from of their own internal dependencies.

    ES Modules are widely supported by all modern bundlers and can be worked around in node environments.

    We may choose to revisit this solution in the future if we find any unintended condequences, but we see this as a pretty sane path forward which should lead to some major bundle size decreases, saner API's and simpler package architecture.

    Please reach out to #fabric-build (if in Atlassian) or create an issue in Design System Support (for external) if you have any questions or queries about this.

8.0.11

8.0.10

8.0.9

  • [patch] Adds missing implicit @babel/runtime dependency b71751b

8.0.8

  • [patch] Adds sideEffects: false to allow proper tree shaking b5d6d04

8.0.6

8.0.5

8.0.4

8.0.3

8.0.2

8.0.1

8.0.0

7.1.3

7.1.2

7.1.1

7.1.0

7.0.1

7.0.0

6.0.3

6.0.1

6.0.0

  • [major] Bump to React 16.3. 4251858

5.2.1

  • [patch] Re-releasing due to potentially broken babel release 9ed0bba

5.2.0

  • [minor] Update styled-components dependency to support versions 1.4.6 - 3 ceccf30

5.1.3

5.1.2

  • [patch] Tabs now abide by selected prop when tabs and selected props both change, instead of using internal selected state 3facabc

5.1.1

  • [patch] Packages Flow types for elements components 3111e74

5.1.0

  • [minor] Add React 16 support. 12ea6e4

5.0.1

  • [patch] fix tabs so that it re-renders when content props update 9b039dd

5.0.0

  • [major] Re-write tabs to provide a more flexible API. Breaking changes: 1) The package no longer exports TabsStateless. The Tabs component manages its own state by default, but will behave as a controlled component if the selectedTab prop is set. 2) The component no longer recognises the defaultSelected property on individual tab objects. Tabs now takes a defaultSelectedTab prop which accepts either a tab object or tab index. 3) The tabs prop is now required - the component will not render if this prop is not set. 4) It is no longer possible to render Tabs without a tab being selected. If the defaultSelectedTab and selectedTab props are not set the first tab will be selected by default. 10a5a5a

4.1.0

  • [minor] Update type for label to accept string 0d0ca5f

4.0.5

  • [patch] Migrate to ak-mk-2 4c679a0

4.0.4 (2017-11-17)

  • bug fix; bumping internal dependencies to latest version (f87bb04)

4.0.3 (2017-10-26)

  • bug fix; fix to rebuild stories (793b2a7)

4.0.2 (2017-10-22)

  • bug fix; update styled-components dep and react peerDep (6a67bf8)

4.0.1 (2017-10-04)

  • bug fix; tabs now hide overflow, and ellipsis text-overflow (issues closed: #ak3519) (aa91734)

4.0.0 (2017-08-11)

  • bug fix; fix the theme-dependency (db90333)
  • breaking; affects internal styled-components implementation (d14522a)
  • breaking; implement dark mode theme (d14522a)
  • bug fix; fix prop types (8abfd3c)
  • bug fix; make tab types clearer (3071418)
  • bug fix; move babel-plugin-react-flow-props-to-prop-types to devDep (e1cd3aa)
  • feature; dark mode for Tabs, plus a bunch of cleanup for the component and its docs (a111cf2)

3.0.0 (2017-08-11)

  • breaking; affects internal styled-components implementation (d14522a)
  • breaking; implement dark mode theme (d14522a)
  • bug fix; fix prop types (8abfd3c)
  • bug fix; make tab types clearer (3071418)
  • bug fix; move babel-plugin-react-flow-props-to-prop-types to devDep (e1cd3aa)
  • feature; dark mode for Tabs, plus a bunch of cleanup for the component and its docs (a111cf2)

2.4.2 (2017-07-27)

  • fix; rename jsnext:main to jsnext:experimental:main temporarily (c7508e0)

2.4.1 (2017-07-25)

  • fix; use class transform in loose mode in babel to improve load performance in apps (fde719a)

2.1.0 (2017-07-17)

  • fix; rerelease, failed prepublish scripts (5fd82f8)

2.1.0 (2017-07-17)

  • feature; added ES module builds to dist and add jsnext:main to most ADG packages (ea76507)

2.0.0 (2017-05-30)

  • refactor tabs to styled-components. Rename StatelessTabs named export to TabsSta (b77172d)
  • breaking; Rename StatelessTabs named export to TabsStateless for consistency.
  • ISSUES CLOSED: #AK-2396

1.3.3 (2017-05-26)

  • fix; add prop-types as a dependency to avoid React 15.x warnings (92598eb)
  • fix; pin react-lorem-component version to avoid newly released broken version (6f3d9c6)

1.3.2 (2017-04-27)

  • fix; update legal copy to be more clear. Not all modules include ADG license. (f3a945e)

1.3.1 (2017-04-26)

  • fix; update legal copy and fix broken links for component README on npm. New contribution and (0b3e454)

1.3.0 (2017-04-20)

  • feature; removed explicit style! imports, set style-loader in webpack config (891fc3c)

1.2.8 (2017-03-23)

  • fix; empty commit to force release of tabs (47d958e)

1.2.6 (2017-03-21)

  • fix; maintainers for all the packages were added (261d00a)

1.2.5 (2017-02-22)

  • fix; trigger onSelect prop on keyboard nav (71bb315)

1.2.4 (2017-02-10)

  • fix; render tabs with flex content correctly in FF and IE11 (dc181da)

1.2.2 (2017-02-07)

  • fix; Updates docs to use https to load demo image (0468d4d)
  • fix; small design fixes for tabs (d3a6666)

1.2.0 (2017-02-03)

  • fix; support centering of tab flex children (87fe198)
  • feature; support fitting tabs inside a flex box container (4158cd8)