Notification

Notification is used to provide feedback to the user about activities, processes, and events in the application.

Usage
Styling

Theme Variants
Duration
Position
Stacking
Size
Interactive Elements
Icons & Other Rich Formatting
Static Helper
Best Practices
Related Components

Notification is used to provide feedback to the user about activities, processes, and events in the application.

const notification = Notification.show('Financial report generated', {
  position: 'middle',
  duration: 0,
});

Theme Variants

Notification comes with a few theme variants: success; warning; error; primary; and contrast. These variants are described in the following sub-sections:

Success

The success theme variant can be used to display success messages, such as when a task or operation is completed.

Open in a
new tab

const notification = Notification.show('Financial report generated', {
  position: 'middle',
  duration: 0,
  theme: 'success',
});

Users shouldn’t be notified always, or even frequently, of successful operations. Too many notifications can be more distracting than helpful to users. Use success notifications only for operations whose successful completion may otherwise be difficult to discern.

Warning

The warning theme variant can be used to display warnings.

Open in a
new tab

{/* The duration is set to 0-sec to prevent the notification from auto-close. */}
<Notification
  theme="warning"
  duration={0}
  position="middle"
  opened={notificationOpened}
  onOpenedChanged={(event) => {
    setNotificationOpened(event.detail.value);
  }}
>
  <HorizontalLayout theme="spacing" style={{ alignItems: 'center' }}>
    <div>
      Your session will expire in 5 minutes due to inactivity.
      <br />
      Close this warning to continue working.
    </div>

    <Button theme="tertiary-inline" onClick={() => setNotificationOpened(false)}>
      <Icon icon="lumo:cross" />
    </Button>
  </HorizontalLayout>
</Notification>

Warning notifications should be persistent, and provide the user with a button that closes the notification or allows the user to take appropriate action.

Error

The error theme variant can be used to display errors.

Open in a
new tab

{/* The duration is set to 0-sec to prevent the notification from auto-close. */}
<Notification
  theme="error"
  duration={0}
  position="middle"
  opened={notificationOpened}
  onOpenedChanged={(e) => setNotificationOpened(e.detail.value)}
>
  <HorizontalLayout theme="spacing" style={{ alignItems: 'center' }}>
    <div>Failed to generate report</div>
    <Button
      theme="tertiary-inline"
      onClick={() => setNotificationOpened(false)}
      aria-label="Close"
    >
      <Icon icon="lumo:cross" />
    </Button>
  </HorizontalLayout>
</Notification>

Error notifications should be persistent, and provide the user with a button that closes the notification or allows the user to take appropriate action.

Notifications are non-modal and can be ignored. Therefore, they’re usually inappropriate for displaying unexpected technical errors that prevent the application from functioning, or situations that require immediate user action. Use instead a modal Dialog in such situations.

The built-in error message feature, included with input field components, should be used for field-specific input validation errors.

Primary

The primary theme variant can be used for important informational messages or to draw extra attention to a notification.

Open in a
new tab

const notification = Notification.show('New project plan available', {
  position: 'middle',
  duration: 0,
  theme: 'primary',
});

Contrast

The contrast variant can improve legibility and distinguish the notification from the rest of the UI.

Open in a
new tab

const notification = Notification.show('5 tasks deleted', {
  position: 'middle',
  duration: 0,
  theme: 'contrast',
});

Duration

By default, notifications stay on-screen for five seconds. The duration can be set — in milliseconds — and should be done so based on the content and its importance:

Use short durations for notifications that contain short text, are of lesser importance (e.g., operations that finished without errors), and have no interactive elements.
Use longer durations for notifications that contain longer text, are of higher importance (e.g., errors), and have interactive elements (e.g., links or "undo" actions).

A duration of at least five seconds (i.e., 5000 milliseconds) is recommended — this is why it’s the default — to ensure that the user has a chance to read and understand the notification.

Persistent Notifications

Setting the duration to 0 milliseconds disables auto-closing. It keeps the notification visible until it’s explicitly dismissed by the user. This should be used for notifications that provide vital information to the user, such as errors.

Persistent notifications should contain a Button that closes the notification, or allows the user to take appropriate action. Less-important notifications shouldn’t be persistent, and instead disappear automatically after an appropriate delay.

Position

Notifications can be positioned in the viewport in seven non-stretched positions, or stretched across the top or bottom:

Open in a
new tab

Use the position attribute in HTML templates (e.g., <vaadin-notification position="top-end"></vaadin-notification>).

<Button onClick={() => show('top-stretch')}>top-stretch</Button>
<Button onClick={() => show('top-start')}>top-start</Button>
<Button onClick={() => show('top-center')}>top-center</Button>
<Button onClick={() => show('top-end')}>top-end</Button>
<Button onClick={() => show('middle')}>middle</Button>
<Button onClick={() => show('bottom-start')}>bottom-start</Button>
<Button onClick={() => show('bottom-center')}>bottom-center</Button>
<Button onClick={() => show('bottom-end')}>bottom-end</Button>
<Button onClick={() => show('bottom-stretch')}>bottom-stretch</Button>

Top End or Bottom Start are recommended for most notifications. They’re unobtrusive, but still noticeable. Middle is the most disruptive position, and should be used only for important notifications, such as errors. Bottom End is the least obtrusive position, but can go unnoticed. Stretch notifications, which span the full width of the viewport, are disruptive, and should be reserved for important notifications whose content requires more space.

Applications with a notification button, or a drop-down in the header or footer, should position notifications to appear in the same part of the screen. For a consistent user experience, use one or two positions throughout the application. Avoid using positions that may obstruct important parts of the UI, such as navigation.

Stacking

Multiple simultaneously displayed notifications are stacked vertically. The ordering of them, though, depends on their positioning.

When using the bottom half of the screen as the position, a new notification appears below the older notifications. With the position set to the top half, a new notification appears above the existing notifications.

Size

The notification card is automatically sized based on its content.

In large viewports, the card’s maximum width is one-third of the viewport. In small viewports, the card always consumes the entire width of the viewport.

Interactive Elements

Notifications can contain interactive content (e.g., Buttons or links) that allow the user to perform related actions.

For example, if an operation fails, the error notification could offer the user the opportunity to try again. Or it could contain a link to a view that allows the user to resolve the problem.

Open in a
new tab

{/* The duration is set to 0-sec to prevent the notification from auto-close. */}
<Notification
  theme="error"
  duration={0}
  position="middle"
  opened={notificationOpened}
  onOpenedChanged={(e) => setNotificationOpened(e.detail.value)}
>
  <HorizontalLayout theme="spacing" style={{ alignItems: 'center' }}>
    <div>Failed to generate report</div>
    <Button
      theme="tertiary-inline"
      style={{ marginLeft: 'var(--lumo-space-xl)' }}
      onClick={close}
    >
      Retry
    </Button>

    <Button theme="tertiary-inline icon" onClick={close} aria-label="Close">
      <Icon icon="lumo:cross" />
    </Button>
  </HorizontalLayout>
</Notification>

In situations where the user might want to revert an action, display an "Undo" button.

Open in a
new tab

<Notification
  theme="contrast"
  duration={10000}
  position="middle"
  opened={notificationOpened}
  onOpenedChanged={(event) => {
    setNotificationOpened(event.detail.value);
  }}
>
  {() => (
    <HorizontalLayout theme="spacing" style={{ alignItems: 'center' }}>
      <div>5 tasks deleted</div>
      <Button
        theme="tertiary-inline"
        style={{ marginLeft: 'var(--lumo-space-xl)' }}
        onClick={close}
      >
        Undo
      </Button>

      <Button theme="tertiary-inline" aria-label="Close" onClick={close}>
        <Icon icon="lumo:cross" />
      </Button>
    </HorizontalLayout>
  )}
</Notification>

Notifications can also contain links to relevant information.

Open in a
new tab

{/* The duration is set to 0-sec to prevent the notification from auto-close. */}
<Notification
  duration={0}
  position="middle"
  opened={notificationOpened}
  onOpenedChanged={({ detail: { value } }) => setNotificationOpened(value)}
>
  <HorizontalLayout theme="spacing" style={{ alignItems: 'center' }}>
    <div>
      Jason Bailey mentioned you in <a href="#">Project Q4</a>
    </div>

    <Button theme="tertiary-inline" aria-label="Close" onClick={close}>
      <Icon icon="lumo:cross" />
    </Button>
  </HorizontalLayout>
</Notification>

Keyboard-Accessible

Make sure that keyboard-only users can access interactive elements in notifications.

Make the notification persistent to prevent it from disappearing before the user has had a chance to react. Provide a keyboard shortcut — either to trigger the action itself or to move focus to the notification card — in cases where multiple interactive elements are present. Finally, make the shortcut discoverable, for example, by displaying it as part of the notification’s content.

Open in a
new tab

useEffect(() => {
  const onKeyDown = (event: KeyboardEvent) => {
    if (notificationOpened && (event.metaKey || event.ctrlKey) && event.key === 'z') {
      event.preventDefault();
      close();
    }
  };

  document.addEventListener('keydown', onKeyDown);

  return () => {
    document.removeEventListener('keydown', onKeyDown);
  };
}, [notificationOpened]);

const renderer = () => (
  <HorizontalLayout style={{ alignItems: 'center' }}>
    <div>5 tasks deleted</div>
    <Button style={{ marginLeft: 'var(--lumo-space-xl)' }} theme="primary" onClick={close}>
      Undo
      {isMac ? '⌘' : 'Ctrl-'}Z
    </Button>
  </HorizontalLayout>
);

return (
  <>
    <Button disabled={notificationOpened} onClick={open}>
      Show notification
    </Button>

    <Notification
      theme="contrast"
      duration={10000}
      position="middle"
      opened={notificationOpened}
      onOpenedChanged={(e) => setNotificationOpened(e.detail.value)}
    >
      {renderer}
    </Notification>
  </>
);

Icons & Other Rich Formatting

Icons and other content formatting can be used to provide information and helpful visual cues. For example, you might do this to make error and success notifications easier to distinguish for users with color blindness.

Open in a
new tab

Unresolved directive in <stdin> - include::../../../../frontend/demo/component/notification/notification-rich-preview.ts[]

Open in a
new tab

<Notification
  theme="success"
  position="middle"
  opened={openedNotifications.includes(0)}
  onOpenedChanged={(e) => {
    if (!e.detail.value) {
      close(0);
    }
  }}
>
  <HorizontalLayout theme="spacing" style={{ alignItems: 'center' }}>
    <Icon icon="vaadin:check-circle" />
    <div>Application submitted!</div>
    <Button style={{ margin: '0 0 0 var(--lumo-space-l)' }} onClick={() => close(0)}>
      View
    </Button>
    <Button theme="tertiary-inline" onClick={() => close(0)} aria-label="Close">
      <Icon icon="lumo:cross" />
    </Button>
  </HorizontalLayout>
</Notification>

<Notification
  theme="error"
  position="middle"
  opened={openedNotifications.includes(1)}
  onOpenedChanged={(e) => {
    if (!e.detail.value) {
      close(1);
    }
  }}
>
  <HorizontalLayout theme="spacing" style={{ alignItems: 'center' }}>
    <Icon icon="vaadin:warning" />
    <div>Failed to generate report</div>
    <Button style={{ margin: '0 0 0 var(--lumo-space-l)' }} onClick={() => close(1)}>
      Retry
    </Button>
    <Button theme="tertiary-inline" onClick={() => close(1)} aria-label="Close">
      <Icon icon="lumo:cross" />
    </Button>
  </HorizontalLayout>
</Notification>

<Notification
  position="middle"
  opened={openedNotifications.includes(2)}
  onOpenedChanged={(e) => {
    if (!e.detail.value) {
      close(2);
    }
  }}
>
  <HorizontalLayout theme="spacing" style={{ alignItems: 'center' }}>
    <Avatar name="Jason Bailey" />
    <div>
      <b>Jason Bailey</b> mentioned you in <a href="#">Project Q4</a>
    </div>
    <Button theme="tertiary-inline" onClick={() => close(2)} aria-label="Close">
      <Icon icon="lumo:cross" />
    </Button>
  </HorizontalLayout>
</Notification>

<Notification
  position="middle"
  opened={openedNotifications.includes(3)}
  onOpenedChanged={(e) => {
    if (!e.detail.value) {
      close(3);
    }
  }}
>
  <HorizontalLayout theme="spacing" style={{ alignItems: 'center' }}>
    <Icon icon="vaadin:check-circle" style={{ color: 'var(--lumo-success-color)' }} />
    <div>
      <b style={{ color: 'var(--lumo-success-text-color)' }}>Upload successful</b>
      <div
        style={{
          fontSize: 'var(--lumo-font-size-s)',
          color: 'var(--lumo-secondary-text-color)',
        }}
      >
        <b>Financials.xlsx</b> is now available in <a href="#">Documents</a>
      </div>
    </div>
    <Button theme="tertiary-inline" onClick={() => close(3)} aria-label="Close">
      <Icon icon="lumo:cross" />
    </Button>
  </HorizontalLayout>
</Notification>

Static Helper

For simple, one-off notifications, it’s convenient to use the static show() helper method. The helper manages the notification’s lifecycle, and adds and removes it from the DOM, automatically.

Open in a
new tab

// Show a simple text-based notification
Notification.show('Financial report generated', {
  position: 'middle',
});

Best Practices

Use Sparingly

Notifications are disruptive by design and should be used sparingly. Use fewer notifications by reserving them for more-important information that might otherwise go unnoticed by the user.

Less-urgent notifications can be provided through a link or a drop-down in the application header or footer, instead of via immediate notifications.

Open in a
new tab

<ContextMenu
  openOn="click"
  renderer={() => <div style={{ padding: 'var(--lumo-space-l)' }}>Show notifications here</div>}
>
  <Button aria-label="notifications" theme="tertiary">
    <Icon icon="vaadin:bell-o" />
    <span style={{ position: 'absolute', transform: 'translate(-40%, -30%)' }}>
      <span {...{ theme: 'badge error primary small pill' }}>4</span>
    </span>
  </Button>
</ContextMenu>

Limit Content Length

Notifications should be brief and to the point. Try to limit the content to one or two lines. More information can be provided through an embedded link or Button.

Component	Usage Recommendation
Dialog	Dialog should be used instead of Notification for anything that requires immediate user action.

Component

Usage Recommendation

Dialog

Dialog should be used instead of Notification for anything that requires immediate user action.

Docs

Docs

Notification

Theme Variants

Success

Warning

Error

Primary

Contrast

Duration

Persistent Notifications

Position

Stacking

Size

Interactive Elements

Keyboard-Accessible

Icons & Other Rich Formatting

Static Helper

Best Practices

Use Sparingly

Limit Content Length

Docs

Theme Variants

Success

Warning

Error

Primary

Contrast

Duration

Persistent Notifications

Position

Stacking

Size

Interactive Elements

Keyboard-Accessible

Icons & Other Rich Formatting

Static Helper

Best Practices

Use Sparingly

Limit Content Length

Related Components