Skip to end of banner
Go to start of banner

Tabs

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 34 Next »

Description

ONGOING 

Tabs enable content organisation at a high level, such as switching between views, data sets, or functional aspectsAllowing user for dual screen support, and workspace customisation.

Types

TypeExample

Main Tabs

Use it as a tabbed navigation - Single row above their associated content


2nd Level Tabs

Single row above their associated content


Details Pane Tabs

Single row above their associated content in the details pane


Ribbon Tabs

TBD

Usage & Behavior

Present tabs as a single row above their associated content. 
Tabs can be switched by clicking on a different tab.
Each tab label describes the content contained within it. Labels are concise and use no more than two words. Keep in mind that at mobile widths and during translation, the character length of a label will impact the experience. Do not use icons in tab labels.

Labels

  • Each tab label describes its content and sets user expectations.
  • Tabs with related content should be grouped adjacent to each other
  • Labels are concise and use one to two words maximum.
  • Tab labels should succinctly describe the content within.
  • Icons are not permitted in tab labels.

Structure

The horizontal layout of the tab bar never changes. The tabs always appear side by side

The NavigationView pane can contain:

Navigation view top pane anatomy

  1. Navigation items
  2. Separators


Number of tabs

A maximum of four tabs may be displayed. This is to maintain an uncluttered UI and reduce cognitive load for users.

Order

Tab order should be consistent across an experience. Tabs with related content should be grouped adjacent to each other.

Implement the focus as follows

  • By default, show the first tab as open. This is the initial setting provided by the control.
    Note: Technically, you can also override the initial selection. However, this is not recommended.
  • Later on, you can show the tab last selected by the user.

Additional guidelines

  • Do not display a loading indicator above the tab while the number for the item count is loading.
  • Handle empty tabs as follows:
    • Hide tabs that do not contain any information, and do not allow the user to create content..
    • Show empty tabs that allow users to create content, such as notes or attachments.
  • Only use the tab bars to navigate between tabs. Do not use any other navigation links. For example, do not let users click an item in tab A that takes them to tab B. This type of cross-navigation inside a container is confusing, and cannot be handled by the back navigation.

States

Main tabs

2nd level tabsDetails pane tabsRibbon tabs

Current appearances in our products


Resources

https://tympanus.net/Development/TabStylesInspiration/

https://material.io/guidelines/components/tabs.html


Needs to be designed


TBD - Open issues

  • Maximum tab number - vertical and horizontal
  • Scroll tab - out of the window
  • Tab + Filter - how it works together
  • Align tab solutioan between mobile and desktop (card / line)
  • Tab title - text / icon / icon and title
  • Missing connection between the current tab to the content area in horizontal
  • Decide about maximum letter on title

Next Steps/Tasks

  • UX design
  • To see full view of tab with other components
  • General suggestion - implementation more interaction for update system to today design

New LUX design 

  • No labels