-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When the maxSelectedItems is set, the widget will not open the popup when the max number of items are selected #1013
Comments
The scenario is still reproducible with R3 2017. I would like to point down a change in the current behavior though, to avoid confusion upon future testing. Due to a breaking change in 2016 R3, "The widget with a single tag mode will deselect all selected items on Backspace or Delete keyboard press." Before that, as visible in the Dojo above, pressing Backspace clears items one by one. Now backspace deletes all of them and it is expected. |
This is still happening with 2020.2.617. We use a single tag mode to prevent the widget from growing huge when the user selects more than one or two items. Once they hit the maxSelectedItems and close the widget, they are no longer able to interact with the widget other than by clicking the 'x' to clear all selections and start over. Any chance this will be implemented? If the multi select uses tagMode:single, the user needs to be able to open the widget in all situations in my opinion. I understand that there might need to be some other visual cue that lets them know that they are no longer able to select items when they click. |
@devineloper Thank you for your feedback. I am increasing the issue priority based on your report as well. We cannot provide a certain timeframe for issues' completion. Once they are moved into development, this will be noted in the issue. |
When the maxSelectedItems is set, the widget will not open the popup when the max number of items are selected. Can be reproduced here:
http://dojo.telerik.com/@veselints/uZeHIbiX
The text was updated successfully, but these errors were encountered: