When I click on the CheckBox's label, "Select All," the dropdown closes. While if I click the TelerikCheckBox itself, it remains open.

Our issue is when we are using OnRead for fetching data based on the entered text, the keyboard navigation is not working. The scroll mode is virtual. The volume of data will be large.

Testing this Select All Checkbox sample in Safari produces a different result compared to other browsers.

Click on the CheckBox in the MultiSelect Header Template closes the popup in Safari. In other browsers (e.g. Chrome, Firefox) the popup remains open after checking the SelectAll CheckBox.

Description

In Firefox, there are occasions in which multiple items remain focused (k-focus class is not removed from the blurred item)

Reproduction (if bug)

1. Create a multiselect and set AutoClose="false".
2. Open the component and select a few items.
3. Close the component.
4. Open the component and select a new item.
5. Two items have the k-focus class.

Second related case:

1. Create a multiselect and set AutoClose="false".
2. Open the component and navigate up and down with the keyboard arrows.
3. Select an item.
4. The last focused item with the arrows is focused as well as the newly selected item.

REPL for reproduction

Expected (if bug)

Only one item should have the k-focus class at a time.

Browser (if bug)

Firefox

Broken Telerik UI for Blazor version (if bug)

3.5.0

The following, took a bit of effort to identify where the behaviour was failing for a screen reader.

 

for all scenarios below the multi-select component currently has items (more than one) in it as selected.

 

GOOD

if keyboard focus is on text edit, and u leave the component (w/ tab key), when revisiting the component (w/ shift+tab keys) all selected items are read out correctly

 

BAD

if keyboard focus is on selected item, and u leave the component (w/ tab key), when revisiting the component (w/ shift+tab key) the focused (selected) item is not read out correctly.

(sorry example read out not provided)

GOOD

selected items are read out correctly when;

• closing items panel w/ escape key,
• closing items panel when selecting an item
  

 

BAD

delete item;

• remove all selected items w/ escape key does not inform a screen reader user of the outcome; that no item is now selected (should state something).

• removing last item with backspace does not inform screen reader of the outcome; that no item is now selected (should state something). I swear this worked once with firefox.
  

the following behaviour also occurs after removing all items via a keyboard, the keyboard focus becomes lost;

• (BAD) most times u can't press a right / down key into the text section of the multi-select (experienced w/ firefox too)
• (GOOD) most times can press alt+down to bring the panel (experienced w/ firefox too)
• (GOOD) u can still tab out to next clickable object

When @bind-Value is used, the tags are ordered in the way the user chose them, which is the expected behavior.

When you don't use two-way binding, but alter the Value in the ValueChanged event (to implement some logic), the tags get reordered according to the their occurrence in the data source.

I would expect that they remain the user order in all cases.