Hi Support Team, Current, we are facing a problem when using "kendo ComboBox" and options in attachment. To reproduce this issue, you have to run sample(kendoui.web.2013.1.319.commercial\examples\web\combobox\index.html) from attachment on safari of iPad. Step by step: 1. Click on arrow icon to expand items 2. Click on textbox 3. Type data to search items near the last item on textbox Actual: ComboBox don't auto scroll to item of user typed.
If you're trying to create an accessible form, "the value of the for attribute must be the same as the value of the id attribute of the form control" [1]. Since the ComboBox widget generates a new element and hides the original select element, the for attribute no longer matches this new input element. I think it would be good if the ComboBox widget would somehow keep the for attribute of the associated label element in sync with the newly generated input element. [1]: http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/H44
ComboBox and DropDown are different because the first allows you to enter values non in list, but if you are using Cascading ComboBox, entering a value non in list in the first choice, the second choice is disabled. I'like to have cascading for values in list with option for inserting values non in list.
Currently it is not possible to show the filter row until some data has been received and the dropdown is visible. Please enhance/change the DropDownList widget so that it will be possible the enter a filter expression before any data is queried. Related forum post: http://www.telerik.com/forums/server-filtering-how-to-not-query-data-until-filter-has-been-provided
Not showing the selected items externally , only within the drop down.
Now autocomplete can not use to suggest email input, just like I input my name, the widget can show myname@xxx1.com, myname@xxx2.com, myname@xxx3.com like this, and the data will be only [{"email":"@xxx1.com"},{"email":"@xxx2.com"},{ "email":"@xxx3.com"}]
Currently when a combo box is used on an edit form, when the combo box first loads, the value property it is bound to (e.g. an int id) is displayed as the text until the databound event fires, and the text value associated with that value can be loaded. It gives the combo boxes an unprofessional look, as they briefly display a number until they are done loading. It also creates some other problems when you have a custom filter function, as described here: http://www.telerik.com/account/support-tickets/view-ticket.aspx?threadid=781390 I recognize that you would not want to change the default behavior since it would be a breaking change, but could you add a flag to toggle this behavior off. You could add a property called "DefaultTextToValue" which is set to True by default, and if you set to false, the display would remain blank until the text value was set by the databound event.
Hi guys! I am glad to be back with another feature suggestions for future Kendo UI releases. I am currently working on a project for a client using Kendo UI Multiselect control. The client's pizza ordering system has an interesting feature for selecting double or single portion ingredients. Currently, I'm only able to display the selected items individually, so what it means is that in the selected items, you see 2 of those same items. Perhaps in the future release, can you have some sort of checking to see if there is double entries, and group those into something like "Cheese (x2)". Honestly, this will make Multiselect so much more cooler!! And when the user decides to click on the "X" beside the item with double items, it simply removes one of the selected items by removing the ",id", and then removes the (x2) text. And ofcourse, for better user experience, Kendo UI Multiselect should automatically calculate the number of a single id has been added everytime the user selects the same item.
I would like to assign multiple values to "dataTextField" property as a part of kendoAutoComplete widget initialization process. This will enable to search and filter values across multiple data fields.
The default behaviour of select elements is to open up with a space-keypress when the elemented is selected (focused).
The keyboard navigation in drop down lists is currently inconsistent based on the widget configuration. When not filterable, the drop down allows you to type the first letter of one of the options in order to select it when the drop down is closed. For example, tab to the drop down, do not open it, and type 'b' to select Bob. When the drop down is filterable, that behavior does not work. You must use alt-down to expand the drop down and then begin filtering. I propose that the widget can consistently handle both cases by detecting whether the drop down is currently open in the keydown handler. If filterable, and open, move into the filtering logic. If filterable, and closed, stick with the standard selection logic.
When bound to oData, the autocomplete contains filter should treat each WORD as a new "substringof"....or make a new odata advanced contains type\property. This is more what users expect when searching...and the odata spec has it covered. http://www.kendoui.com/forums/ui/autocomplete/odata-google-like-filter.aspx
Please consider adding pagination to the multi-select dropdown and also the select all, deselect all options to appear inside the dropdown instead of below the input field.
Currently multiselect increases its height to accommodate all selected values. Can you please provide a way where it reverts back to its height after selecting all values and shows 1 value and count for rest of the values selected? Here is a screenshot: http://s11.postimg.org/ur5qqy5lv/Multi_Select.png You can see it's implementation selecting values in "Type Location or Project" multiselect on Residential Tab http://www.99acres.com/
It would be awesome to have the DropDownList automatically open upon focus and if filtering is enabled the focus/select the filter textbox. This is great from a data entry standpoint where keyboard Navigation like Tab keys are used. Maybe a property lag like OpenOnFocus=true
Need to add configuration to display value which is combination of two or more properties or fields in dataSource. Just like valueTemplate in dropdownlist list but without html tags, like $('#comboboxinput').kendoComboBox({ dataSource:[{Name:"English (US)", Value:"en-US"}, {{Name:" Japanese (Japan)", Value:"ja-JP"}}], template:"<div>#=data.Name+' - '+data.Value#</div>" complexValueFormat:"data.Name+' - '+data.Value" }) I was working on a project where I was asked to display large number of items on dropdown list so i was using template and valueTemplate confugurations, since the items was too large to scroll we decided to use combobox but the problem is unable to display complex values after selecting an item. Currently I'm looping through all items and adding a property DisplayName to each item before setting dataSource. This feature will be very useful and replace dropdownlist if dataSource is too large and complex value is to be displayed.
I would love to see the ability to disable/enable items in the DropDownList dynamically at run time. We have complex validation rules in our UI that need to prevent the user from using certain items if other options are selected. The big problem is the DropDownList doesn't let me enable/disable items or add/remove them. This means instead of having a few change events wired up to enable/disable items, I need to do it in complex validation rules. I think the ability to disable/enable items would be a valuable feature to the kendo framework. Regards, Scott
The combobox currently doesn't react on the disabled-attribute for options. It should be possible to make single options visible but not selectable with this attribute as in original html-select: http://www.w3schools.com/tags/tryit.asp?filename=tryhtml_option_disabled I found no way to do this yet.
I want dropdownlist to have group by with 2 fields
Currently to close the colorPicker manually, we have to do ".kendoColorPicker('close')", however the rest of the dropdowns/combos uses ".kendoPopup('close')". It will be great to support it as well with colorPickers to allow closing of all popup elements on scroll with a uniform solution