Completed
Last Updated: 30 Jan 2020 11:48 by ADMIN
Release 2.7.0
Edward
Created on: 15 Sep 2019 22:16
Category: UI for Blazor
Type: Feature Request
16
Multiselect component
I am very surprised that Multiselect is missing among the list of Blazor controls being offer.  Syncfusion already offers a full-feature Multiselect.  Is a Multiselect on the road map?  When should we expect it.  Currently the only way to have a select list with multiple selections enabled is a pretty ugly JSInterop hack.  I am honestly considering switching to Syncfusion as they seemed to be far ahead of Telerik in Blazor development.
3 comments
ADMIN
Marin Bratanov
Posted on: 18 Nov 2019 15:33

Hello,

I updated its status. We are aiming at R1 2020 - which is January 2020. We may be able to deliver it sooner, we do have releases often, about once a month. You can click the Follow button at the top of the feedback portal page to get email notifications about status updates.

 

Regards,
Marin Bratanov
Progress Telerik

 UI for Blazor
Valid Development Factory
Posted on: 15 Nov 2019 10:10
Is there any ETA on this control? We have an application where we would like to use multiselects.
ADMIN
Marin Bratanov
Posted on: 16 Sep 2019 06:08

Hello Edward,

You can click the Follow button this page for status updates when such a component gets implemented, because this is the first request for it. Features on the grid and components like a scheduler and charts are requested much more often, and this is why we focus on the components with bigger impact and more requests first. We do take the popularity of requests in this portal actively in our roadmap planning, though, and we keep this in mind.

At the time of writing, selection is available in the grid, so you can see if that will fit your needs: docs and demo.

I must also note that Syncfusion wrap jQuery widgets for their Blazor components, while we are creating native components from the ground up. You can read more about the differences in those approaches in the following blog post: https://www.telerik.com/blogs/comparing-native-blazor-components-to-wrapped-javascript-components. We decided to go with the native approach because we believe it is going to yield better results in the long run, even though it will take a bit longer to spin up the number of components and features.

 

Regards,
Marin Bratanov
Progress Telerik

 UI for Blazor