Versions Compared

Key

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

...

Typically, user interaction events are named as follows:

Bottom Sheet

A bottom sheet is displayed to the user.

Button

The user clicks/taps on a button.

Card

The user clicks/taps on a card.

Checkbox

The user checks/unchecks a checkbox.

Chip

The user clicks/taps on a chip.

Dropdown

The user clicks/taps on a dropdown.

Error

An error is triggered after a user action.

Input

The input field gets focused.

Link

The user clicks/taps on a link.

List Item

The user clicks/taps on an item in a list.

Modal

A modal is displayed to the user.

Navigation

The user clicks/taps on a navigation item.

Number Input

The user clicks/taps on one of the interactive elements of the number input component: minus button, plus button or the number field.

Paginate

The user clicks/taps on the pagination button.

Page View

The user lands on a page (URL).

Radio Button

The user clicks/taps on a radio button.

Segmented Button

The user clicks/taps on a segmented button.

Snackbar

A snackbar is displayed after a user action.

Switch

The user clicks/taps on a switch.

Tab

The user clicks/taps on a tab.

Text Area

The text area gets focused.

Standard properties

See Attributes and properties to understand what event properties are. User interaction events typically contain the following standard properties:

Name

While the event defines the component, e.g. Button, the name property specifies which button, e.g. Save

Path

The path URL after the domain, e.g. / (home), /menu, /store-locator/service-mode, etc.

Type

Exclusive property

Exclusive for lists to help better differentiate content like different reward cards by tier, or pages where we might have offers mixed with rewards.

Specific events and properties

...