...
Magnolia also highlights an item, if the mouse or the keyboard focus is currently above a selectable item - it is not highlighting items, which may not be selected at all.
Behaviour description
...
Remarks on different input characteristics
Note that each of the three supported input methods - mouse, keyboard and touch - has its own characteristics. Not , and not all visual feedback and interaction possibilities are supported by alleach.
In particular, you may highlight focus on an item with the keyboard or by hover hovering the mouse on it or by moving the keyboard focus on over it. This is often visualized by softly highlighting the item. Touch devices interfaces, however, do not support highlighting in an intuitive manner, so Magnolia does not support highlighting of items for touch input.moving the focus in the same intuitive manner. By touching an item, you already interact with it and thus you always move both focus and selection to the item. Consequently, Magnolia only supports item selection on touch devices.
On the other hand, selecting Selecting an item is as easy as clicking on it with a mouse or touching it. Selecting multiple items is also easy and intuitive, if we you provide checkboxes next to the items. For these input methodsmouse and touch, you thus have two way ways to select items: you either touch or click the item or click on it, or you mark its checkbox. When using the keyboard, however, the clearest way to handle item selection is to unify both : when you select the item by pressing a key, you also immediately mark its checkboxinteractions, since you always have to at least press a key to select an item. Magnolia thus also always toggles an item's checkbox on selection when using the keyboard.
If any of this is not entirely clear, please refer to the more detailed explanations and the matrix in the paragraphs below.
...
Description of desired behavior
Focus an item
An item (and its context) is visually highlighted on is focused on hovering the mouse over it or by moving the keyboard focus on the item using one of the arrow keys (UP, RIGHT, DOWN, LEFT).
Highlighting Focusing an item mainly indicates visually highlights it indicating that the item could also be selected.
If an item is only highlighted, no When the same item remains focused, details on it are shown anywhere in the interface - the visual marker merely makes it clear that the item could be selected. The reason we show no details after a delay in any enabled and visible item details view elsewhere on the interface. The reason for the delay is to prevent the interface from changing too rapidly on quick focus changes, to keep it responsive and to prevent high load on the server.
Select a single item
A single item may be selected by clicking on it, touching it or by hitting the SPACE bar . Alternatively, for interfaces which allow when it has the focus. If an interface supports selecting multiple items, it thus shows a checkbox next to the item an item. Thus, alternatively, this checkbox may be checked to select the item. In both cases, a stronger strong visual marker marks the items as "selected". around the item signals its selection.
So, while an item may be selected without checking its checkbox if you use mouse or touch input, its checkbox is always toggled if you select the item using the keyboard.
In addition, any visible and enabled view for item details will refresh immediately and show additional details on the just selected item.
Select multiple items
To select multiple items, you repeatedly select single items using their checkboxes until all the item you intend to select your items are selected.
For views Views supporting the selection of multiple items , there's shall also always a offer an additional checkbox available to toggle the selection of all items (visible or currently unvisible invisible) in the view. Checking it first selects all items, checking it again de-selects the items.
Executing an operation on selected items
If a view allows to select items, it always also offers operations to be executed on them. Selecting one or multiple items enables only those operations, which are defined on the list of selected items. For any view showing operations, it should be visually very obvious, which operations are currently enabled available and which are not.
Please note that it is not acceptable to simply attempt to execute an operation and to return a failure an error if it is detected that the operation has been undefined for one of the selected items. Failures Errors should only be returned if executing an operation actually returns an errorfails.
It is highly desirable that an operation is executed atomically on multiple items as this is expected semantically and allows properly supporting the undo functionality we plan to introduce with 5.0.
...