When using the minLength configuration setting, a ComboBox initially respects the minLength and does not bind or filter data (dataBound & filtering event handlers not called) until the minLength is reached by the combo's text.
However, when deleting text from the input, the minLength works until all the text is deleted. At that point (there is no longer any text in the input), the event handlers for dataBound & filtering are called even though the length is 0 (ie. not at minLength).
Is this a bug or is there a way for the minLength to continue to work when all text has been removed? This behaviour can be seen using an example from the Dojo: http://dojo.telerik.com/aPEba
This becomes more problematic when the data that is bound is much larger, hence the use of the minLength configuration for search.
However, when deleting text from the input, the minLength works until all the text is deleted. At that point (there is no longer any text in the input), the event handlers for dataBound & filtering are called even though the length is 0 (ie. not at minLength).
Is this a bug or is there a way for the minLength to continue to work when all text has been removed? This behaviour can be seen using an example from the Dojo: http://dojo.telerik.com/aPEba
This becomes more problematic when the data that is bound is much larger, hence the use of the minLength configuration for search.