Rank 2
Iron
Veteran
- Initialize the combo (assuming it's already populated in the markup as a select->option with text and values)
$("#combo").kendoComboBox({filter:"contains"}); - Add a couple of characters to the end of the first item, thereby making it "technically" invalid as it's not an item in the combo
- Click your button to validate
- Passes
- Pick a new item from the combo
- Add a couple characters to the end
- Click button again
- Fails validation
11 Answers, 1 is accepted
I am not sure that I was able to understand where the issue exactly is. Could you please provide a test project which replicates the problem?
Georgi Krustev
the Telerik team
Rank 2
Iron
Veteran
The problem is that once I change the text on the first combo item, it should invalidate that item...because it's not a valid selection anymore. This is how it works when you select another item in the list, but on load the first item always passes validation.
The ComboBox widget does not have any built-in validation functionality. Could you please provide a code snippet which shows the current implementation? Thus I will be able to observe it locallly and advice you further.
Georgi Krustev
the Telerik team
Rank 2
Iron
Veteran
Video: http://screencast.com/t/Vz2ilH3kNUDG
Fiddle: http://www.screencast.com/t/YA0pfvmZp
With "contains" the moment I change the text and there's no item in the combo that matches, it should fail validation.
Rank 2
Iron
Veteran
Thank you for the screencasts. I believe that this behavior is expected and I cannot confirm it as a bug. The "required" attribute of the select element, means that the validation will pass if there is any value. As you probably know, the combobox widget allows custom value. Hence when you type "Item" the value of the combobox is "Item" and the validation passes. You can prevent custom value wiring the change event and clearing the combobox's value using value method. Check this link for more information.
Georgi Krustev
the Telerik team
Rank 2
Iron
Veteran
When I have a combobox I want to give the users a set of values to pick from, I don't expect\want it to be a freeform text input. If I wanted that, I would have used the AutoComplete instead.
So when I enable filter: "contains" what I would expect would happen is that it allows the user to filter the list, while still maintaining list integrity, not become a freeform text input....since what they type has no value.
Know what I mean?
Rank 2
Iron
Veteran
The logic almost already exists with the placeholder config element
The ComboBox widget is desined to allow entering a custom value. Setting the filter option specifies the filtering functionality of the DataSource and does not prevent entering of the custom value. I will suggest you use a DropDownList widget, which does not allow custom values.
I will log you request to our internal system for further consideration.
Georgi Krustev
the Telerik team
Rank 2
Iron
Veteran
Please consider the feature request, and I'll use your logic to check for a custom value in the meantime
Thanks Georgi
Rank 2
We too wish the ComboBox could filter only through it's available values and have option to not allow custom values since 99% of the time when people need control like this, they really want a dropdown list that has a quick search/autocomplete of the possible values. In our app, the only place where we need a combobox the way it currently works is in one location - to allow people to either enter their own password/security question or select from pre-defined ones. Every time I put a combobox anywhere I need to explain to people how it works and why it lets them enter "crap that's not there".