Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A toolbar is a grouped set of controls used , allowing users to apply perform actions to a on related content.

...

Usage & Behavior

The toolbar may be used in 3 componentsapply to the whole page, or be associated with a data table, list, or chart.

Type

Image

Data Table

Image Removed
Image Added

List

Image Modified

Chart

Image Added

Page

Image Removed
My schedule- group textual.pngImage Added

General guidelines

Structure

  • The toolbar is shown as a horizontal, single row.

  • It may contain one or more controls.

Placement and Positioning

  • The toolbar is located on top of a data container area (e.g. Data the data table), with .

  • It uses the maximum width of the containerdata area.

  • Where possible relevant, the toolbar can should be divided into 2 distinct types of operationstwo areas:

    • LeftAction area - aligned to the left, actions including controls that impact the data (e.g. delete).

    • RightView area - aligned , actions impacting to the right, including controls that impact the view of the data (e.g. print, search, change view mode etc.)

...

    • .
      If there is only a view area, it will be aligned to the left, depending on the context of the user flow.

Content

  • A toolbar can may include:

    • a variety of

    components Search etc…
  • Dialog buttons are not used within a toolbar.

  • Optionally, a mini-hamburger menu button (Itay lapid (Unlicensed) add icon) can be used to aggregate multiple actions in an Action Menus .

  • A toolbar can also include information
    • and a Search component.

    • information items, such as counters and statuses (

    see example in
    • See data table

    image
    • example above).

  • Dialog Buttons cannot be used within a toolbar.

  • If actions can be groupedthere are sets of controls (for example, table-level actions vs. row-level actions), they should be separated by a vertical divider (e.g. table-level actions Vs row-level actions).

  • In case of a large number of items, a three-dotted Icon Button may be used, allowing users to open an Action Menu (see the chart example above). In this case, the icon button will be the last control.

Internal Logic

  • A toolbar Toolbar controls can be applied to single or multiple selection actions on the selected items or the entire related content.

  • Controls in the toolbar Toolbar controls can be enabled\/disabled contextually in response to a data selection (e.g. disabled delete action , a Delete control will be disabled if no row is data was selected).

States

The toolbar itself has no states. Each component control on the toolbar will behave according to its own states.

Validations and errors

The toolbar itself has no validations or errors. Each component control on the toolbar may have its own validations.

Best practices

Use:If the data set management relies on several controls and the actions are valid for the related content

  • if the user can perform actions or change the view of the related content.

  • if the related content allows multi selection.

Don’t use:

  • On a single-selection data table, if all actions can be performed only at a row-level.

  • If a ribbon pattern is used.

General:

  • When Where possible, consider using only icons Icon Buttons, with a corresponding tooltip Tooltips.

  • Icon buttons with text should be used to emphasize one or two specific actions.

...

Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility.

Design

Zeplin link

Screen thumbnail

https://zpl.io/aB4Eedp

Image Modified

Code

...