You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In cases where the app exposes a button to enter the multi-selection mode, it might be undesirable for the selection mode to be automatically turned off after the last item is deselected. Consider the following scenario: The app exposes a "Multi-select" button that enters the selection mode and, in selection mode, exposes a "Cancel" button that exits it.
The user enters selection mode by pressing the multi-select button.
The user selects an item but then quickly deselects it as they want to select a different one.
Desired behavior -> selection mode is still active, and the user can select another item.
Current behavior -> selection mode gets deactivated after the item is deselected, and the user needs to activate it again.
The automated exiting of the selection mode after the last item is deselected might be exposed as a flag so that it can also be turned off when the long-press gesture activates the selection mode. However, that case might be more contentious from the UX perspective.
The text was updated successfully, but these errors were encountered:
In cases where the app exposes a button to enter the multi-selection mode, it might be undesirable for the selection mode to be automatically turned off after the last item is deselected. Consider the following scenario:
The app exposes a "Multi-select" button that enters the selection mode and, in selection mode, exposes a "Cancel" button that exits it.
Desired behavior -> selection mode is still active, and the user can select another item.
Current behavior -> selection mode gets deactivated after the item is deselected, and the user needs to activate it again.
The automated exiting of the selection mode after the last item is deselected might be exposed as a flag so that it can also be turned off when the long-press gesture activates the selection mode. However, that case might be more contentious from the UX perspective.
The text was updated successfully, but these errors were encountered: