Completed
Last Updated: 03 Aug 2017 14:40 by Bibin
Approved
Last Updated: 04 Mar 2018 19:05 by Jon Morris
If the same text is typed into the input field as the one set for EmptyMessage and page is submitted, validator evaluates True.

Current workaround is to subscribe the RadComboBox to OnClientFocus client event handler, and clear the EmptyMessage manually, thus preventing the EmptyMessage text to be sent to server.

<telerik:RadComboBox ... OnClientFocus="comboFocus">

<script type="text/javascript">
	function comboFocus(sender, args) {
		sender.set_emptyMessage("");
	}
</script>
Approved
Last Updated: 10 Oct 2017 16:25 by ADMIN
ADMIN
Created by: Peter Milchev
Comments: 0
Category: ComboBox
Type: Bug Report
3
A possible workaround would be tweaking the ItemRequestTimeout property of the ComboBox

<telerik:RadComboBox ItemRequestTimeout="380" runat="server" ... >
        ...
 </telerik:RadComboBox>
Declined
Last Updated: 10 Dec 2014 05:26 by Yousef Salimpour
Created by: Yousef Salimpour
Comments: 3
Category: ComboBox
Type: Bug Report
3
In ComboBox If somehow focus is moved to dropdown element (e.g. when user clicks on a header, or on load more items button) then arrow keys and keyboard support won't work anymore.
It can be fixed by simply setting dropdown tabindex to say 1 and attaching ComboBox's own _onKeyDown handler to dropdown keydown too.
Completed
Last Updated: 15 Oct 2014 10:16 by ADMIN
In the meantime you can use the following css workaround that will fix the issue: 

.rcbAutoWidthResizer .rcbScroll {
	overflow: visible !important;
}
 
/*To target IE 6, 7 and 8*/
@media \0screen\,screen\9 {
	.rcbAutoWidthResizer .rcbScroll {
		overflow: auto !important;
	}
}
 
/*To target IE 9 and 10*/
@media screen and (min-width:0\0) {
	.rcbAutoWidthResizer .rcbScroll {
		overflow: auto !important;
	}
}
Completed
Last Updated: 08 Aug 2013 15:20 by ADMIN
ADMIN
Created by: Ivan Zhekov
Comments: 1
Category: ComboBox
Type: Bug Report
3
Customer feedback:

The first combobox below behaves as I would expect to, and resizes when the browser window is resized.  However, the second combobox does not resize when the browser window does.  They use the same skin.  The only real difference that I can see is that I use check boxes in the second one.
Approved
Last Updated: 22 Nov 2013 14:08 by Paul Rogers
Created by: Paul Rogers
Comments: 0
Category: ComboBox
Type: Bug Report
2
We are running HTML validators as part of an effort to attain WCAG 2.0 A compliance.

Among the errors we are seeing is

The summary attribute is obsolete. Consider describing the structure of the table in a caption element or in a figure element containing the table; or, simplify the structure of the table so that no description is needed.

Here is a snippet of the failing HTML, apparently from the rendering of the RadSocialShare control:

	<div id="ctl00_TemplateBody_WebPartManager1_gwpciNewSocialShareCommon_ciNewSocialShareCommon_RadSocialShare1_compactPopup_C_comboBox" class="RadComboBox RadComboBox_Default" style="width:160px;">
<table summary="combobox" border="0" style="border-width:0;border-collapse:collapse;">

We are currently running version 2013.2.717.45 of the ASP .NET for AJAX controls, but we just tried 2013.3.1015.45 and it didn't fix things in this regard, either.

There is a similar discussion at http://www.telerik.com/community/forums/aspnet-ajax/combobox/table-summary-attribute.aspx , which recommends a jQuery fix.  This fix works in terms of removing the summary attribute from that table, but it does not result in clean HTML when the w3c validator is run against it, so we believe that is not an acceptable workaround.

In the discussion at http://www.telerik.com/community/forums/aspnet-ajax/general-discussions/accessibility-issues-various.aspx , some mention is made of fixing the combo box for the 2012 Q3 release, but it doesn't look like that happened.
Completed
Last Updated: 05 Nov 2014 14:14 by Elena
Completed
Last Updated: 04 Sep 2019 08:27 by ADMIN
See: https://demos.telerik.com/aspnet-ajax/combobox/examples/accessibility/defaultcs.aspx

1. Click somewhere in the page to establish focus.

2. Use the tab key to focus the combo box.  (This works in Chrome, but in IE the control is skipped.)

3. Note that the combo box does not drop-down the list of options like it does when you click the mouse. Clicking the enter key does not drop down the list. Alt-Down-Arrow does not drop down the list.

4. Press Tab and note that focus skips the arrow icon on the combo box and moves down to the "validate with Wave" link.

5. Press Shift-Tab and note that the Arrow icon is now focuses and the enter key will drop down the options list.

6. While JAWS 2019 is running, press the "C" key and note that JAWS reports that there are no combo boxes on the page.

 

Expectations:

* Jaws is able to properly identify the combo box based on ARIA tags

* Tabbing into the combo box presents the same behaviors as using the mouse button
Completed
Last Updated: 08 Jul 2016 18:42 by Yazan
described in this forum thread-http://www.telerik.com/community/forums/aspnet-ajax/combobox/717802-radcombobox-auto-complete-problem.aspx
Pending Review
Last Updated: 21 Jun 2016 14:52 by Alexandre
Using the client-side requestItems method of a RadComboBox to fire the refresh of it's items(with a call to clearCache before to ensure that the refresh is performed), doesn't always perform the async callback request, sometimes resulting in the "Loading" text being added at the top of the combo's items drop-down and staying there (as the callback to the server is never fired, so it's result never received). 

After quite a bit of trials, I finally managed to figure out that the issue arise when there is an async postback in progress on the page (to refresh an update panel) when requestItems is called.

Stepping through the requestItems call with IE F12 tools, I found that this is due to the fact that the Sys.WebForms.PageRequestManager do not perform callbacks if there is an async postback in progress. I think that the RadComboBox should detect that situation and wait until the end of the async postback to fire it's requestItems callback, otherwise the combo get stuck in the "loading in progress" state, waiting for the end of the callback that will never happens as the PageRequestManager did not start it. Additionally, in F12 Network tab, I can see that there is no request performed for the callback to request the items of the combo-box.

I reproduce the issue with the following steps:
1- Have a page with a RadComboBox, a ScriptManager with partial rendering enabled and an UpdatePanel.
2- In the browser, trigger the async postback to refresh the UpdatePanel
3- From JavaScript, while the async postback is in progress, call the requestItems method of the RadComboBox
4- Open the drop-down of the combo, and you can see the "Loading" text at the top, with the initial list of items. And it stays like this until another call is made to requestItems when there is no async post-back in progress which will actually perform the callback.
Completed
Last Updated: 15 Mar 2016 15:05 by ADMIN
ADMIN
Created by: Ivan Danchev
Comments: 0
Category: ComboBox
Type: Bug Report
1

			
Completed
Last Updated: 19 Sep 2016 12:46 by Adam
Completed
Last Updated: 13 Oct 2015 07:38 by ADMIN
Completed
Last Updated: 12 Aug 2015 08:57 by ADMIN
ADMIN
Created by: Ivan Danchev
Comments: 0
Category: ComboBox
Type: Bug Report
1

			
Approved
Last Updated: 11 Jun 2015 15:26 by ADMIN
ADMIN
Created by: Ivan Danchev
Comments: 0
Category: ComboBox
Type: Bug Report
1

			
Completed
Last Updated: 03 Sep 2019 16:10 by ADMIN
Release R3 2019
Problem:  Latest Telerik version of Combobox or RadCombobox reads "readonly" though it's not, when EnableAriaSupport is enabled.

Details: 

url to test with JAWS - https://demos.telerik.com/aspnet-ajax/combobox/examples/wai-aria-support/defaultcs.aspx

When I use JAWS to read the combobox present on this demo it reads as follows - 
              ComboBox readonly - Alice Mutton. To change the selection press the arrow keys.

Over here, why JAWS is reading "readonly". It's not readonly. It's making our screenreader blind users confusing.

I drilled down more into the problem and found that, the input element below has the aria-readonly=true set though the combobox is not readonly.
Here is the html generated for above combobox from telerik demo site -

<input name="ctl00$ContentPlaceholder1$RadComboBox2" class="rcbInput radPreventDecorate" id="ctl00_ContentPlaceholder1_RadComboBox2_Input" role="combobox" aria-busy="false" aria-disabled="false" aria-expanded="false" aria-haspopup="true" aria-readonly="true" aria-owns="ctl00_ContentPlaceholder1_RadComboBox2_listbox" aria-autocomplete="none" type="text" readonly="readonly" value="Alice Mutton" autocomplete="off">

I understand that this input control should be readonly so that aria users should not type and go haywire. But looks like to maintain the readonly=readonly property, telerik is generating aria-readonly=true for this _Input control and resulting this issue.

When you change this attribute aria-readonly="true" to aria-readonly="false", JAWS read it correctly as follows - 
              ComboBox - Alice Mutton. To change the selection press the arrow keys.

Let me know how to achieve that so that users will not be confused.
1 2 3 4