Is it possible to auto-select an entered value when tabbing out of the MultiSelect Dropdown when AllowCustomValue is enabled?

[David Cook]

Without the user selecting their manually entered custom item in the drop-down or pressing enter when AllowCustomValue is enabled, can it be added to the list of selected items when tabbing/on-blurring out of the control? If not, it is possible to access the user's manually entered text content that hasn't been selected in a MultiSelect Dropdown via an event or a property in a control reference?

[UdhayaKumar Duraisamy]

The requested requirement “Tab to select active item of the list” has already been considered as a feature from our end, but we do not have any immediate plan to implement this feature. At the planning stage for every release cycle, we review all open features and implement the features based on feature rank, customer requested count and volume wish-list.

The status of implementation can be tracked through the below portal link: 

https://www.syncfusion.com/feedback/38452/tab-to-select-active-item-of-the-list

[Ryan Tomko]

 

Same issue.  Please have TAB select the custom value and add it to the underlying datasource.

[UdhayaKumar Duraisamy]

We have considered the reported scenario "Tab Key Does Not Properly Update the MultiSelect" as a bug from our end. The fix for this issue is scheduled to be included in our upcoming release in the first week of January 2025.

You can track the status of this issue through the following link:

Tab Key Does Not Properly Update the MultiSelect in Blazor | Feedback Portal

Disclaimer: “Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization.”

[UdhayaKumar Duraisamy]

We’re pleased to inform you that the issue, "Tab Key Does Not Properly Update the MultiSelect" has been resolved in our release version 28.1.37. We recommend upgrading to latest version to address the issue.

 

Release Notes: Essential Studio for Blazor Weekly Nuget Release Release Notes

Root Cause:

When a custom value was entered and the component lost focus, the InputValue and ListData were not updated, causing the custom values to persist in both the input field and the popup.

Solution:

We have revised the code to ensure that both the InputValue and ListData are updated when the component loses focus.