Related pages: Message Popups

Lead:  Liav Nadler ONGOING 

Description

A toast is a small message box that appears in response to a user or system action. It contains simple feedback about the action, while any current activity remains visible and interactive.

Types

Type	Usage	Example
Info	General information related to an action
Success	Actions that were completed successfully
Warning	System warnings or actions that may cause a problem
Error	System errors or actions that failed to complete
Continuous Action	An action that takes more than 3 seconds (exact duration TBD)

Usage & Behaviour

General guidelines

• Toasts are triggered either by the user (e.g. refreshing a data table) or by the system (e.g. server error)

• The toast appears from the left with a slide effect

• Error toasts stay on the screen until the user actively closes them warnings?

• Other toasts disappear automatically after X seconds with a fade effect (the user can still close them manually)

Structure

• A toast may contain the following elements:

  • An icon representing their type or, in case of a continuous action, an animated progress indicator

  • Text, including a title (optional) and the body of the text

  • A closing button (x)

  • A Cancel button

  • An expand button (see below)

Placement and Positioning

• All toasts appear at the bottom-left end of the screen.

• Toasts have a fixed width.

• The height of a toast depends on the amount of text it contains. In case of more than 3 lines a button will appear, allowing the user to expand the toast.

Interaction

• Clicking the closing button closes the toast with a fade effect.

• When shown, clicking the Cancel button cancels the action and closes the toast. In this case another information toast may appear, indicating that the action was cancelled

• When shown, clicking the expand button:

  • expands the toast upwards with a slide effect, revealing the rest of the text.

  • hides the expand button.

Multiple Toasts

• In case an additional toast appears before the previous one disappeared:

  • If the new toast was the first error toast, it will appear at the bottom of the page, pushing other toasts upwards.

  • If the new toast was another error toast,

  • If the new toast was

Best practices

• Keep the text short and informative

• In case of warning or failure provide the user with a recommendation

Edge Cases

• In case another action occurred before the previous toast disappeared:

  • The new toast will push the previous toast upwards

  • If a lower toast disappeared the upper toasts will move down respectively

Open Issues

• Behaviour across workspaces

• Aggregating notifications

• Continuous processes (more than 10 seconds), minimized toast

Accessibility compliance

<<In general each component should be A11y complied,  please follow the 3 guidelines linked below. At the very least we should document that each component is in compliance with each of the 3>>

Focus management

• While the toast is shown any current activity remains visible and interactive

Screen reader support 

<<Make sure the components support screen reader for content or behaviour where needed - see /wiki/spaces/UX/pages/308248620 >>

Contrast & size compliance

<<Visual designers must comply with the minimal of /wiki/spaces/UX/pages/301498483 for each component>>

Design

Code

<<a box containing the code - discuss with Femi>>