Last Updated: 21 Mar 2023 14:26 by ADMIN
Release 4.2.0 (26/04/2023)
Created on: 15 Feb 2023 18:53
Category: ChipList
Type: Bug Report
Left Arrow key always focuses the first Chip when the Disabled field is not set

Keyboard support is only working properly when the ChipList is bound to a List<ChipModel>.  If you try one of your other demos of the chiplist the following will occur:

  • Right Arrow will navigate to the next chip in the list
  • Left Arrow will navigate to the first chip in the list

I would expect that the Left Arrow will navigate to the previous chip in the list.  (As a side note, I would recommend having the the Down Arrow and Up Arrow mimic Right and Left since a screen reader user won't necessarily know that the chiplist is horizontal.)

An example of the problem can be found in this demo:

Here is a sample where I converted the returned list to List<ChipModel> and bound to that:

In that example, the Left Arrow functions normally.

1 comment
Nadezhda Tacheva
Posted on: 22 Feb 2023 18:09

Hi Mike,

Thank you for reaching out! Please see my comments on the relevant points as follows:

Left Arrow key not behaving as expected

After further investigation and testing on my end, it appears that the issue occurs if the Disabled field of the ChipList is not set. This will happen when the default Disabled field is missing from the model or when the DisabledField property is not set for custom bool field name in the model.

For the time being, you may handle the scenario in one of the following ways:

I'd like to thank you for bringing our attention to this behavior. As a small token of appreciation, I've rewarded your account with some Telerik points.

I also added your vote as we prioritize the fixes based on the community demand apart from their severity. I updated the item status and tweaked the name to cover the specific use case and issue.

Customizing the keyboard navigation

While using the Down Arrow and Up Arrow is not part of our default keyboard navigation for the ChipList, we will be considering an option to allow one to customize the keyboard shortcuts. We are gathering feedback on the matter and I already listed your requirement in the internal item. I also added your vote to the public feature request, so we can properly track the community interest in such functionality.

I hope you will find the above information useful. Please let us know if any other questions appear.

Nadezhda Tacheva
Progress Telerik

Learn about the important changes coming in UI for Blazor 4.0 in January 2023!