Similar to the property in the ComboBox
At the moment RadDropDownList can be bound for a Web Service, but there are no Client Events which allow developers to handle and control actions happening during the data binding process. For example: - Event fired, before the request is made (OnClientItemRequesting). - Event fired, after the response is received (OnClientItemRequested). - Event fired if the request call has failed (OnClientItemRequestFailed).
A workaround is to disable the embedded jQuery and use an older version (for example, 1.11.1 which is the previous version the suite used): https://docs.telerik.com/devtools/aspnet-ajax/controls/scriptmanager/disabling-the-embedded-jquery Repro steps: - Add a dropdownlist, attach server handler - select item Expected: postback Actual: error <asp:Label Text="" ID="Label1" runat="server" /> <telerik:RadDropDownList runat="server" ID="rddl1" OnSelectedIndexChanged="rddl1_SelectedIndexChanged" AutoPostBack="true"> <Items> <telerik:DropDownListItem Text="first" /> <telerik:DropDownListItem Text="second" /> <telerik:DropDownListItem Text="third" /> </Items> </telerik:RadDropDownList> protected void rddl1_SelectedIndexChanged(object sender, Telerik.Web.UI.DropDownListEventArgs e) { Label1.Text = (sender as RadDropDownList).SelectedText; }
add min-dropdownheight and max-dropdownheight to raddropdownlist (to let it "grow" until a max-height
RadDropDownList has an attribute "DropdownWidth" that controls the width of the LIST when it drops down. If you set the width to a specific number of pixels (say 200px) then there is no issue. But if you set it to "100%" then I would have expected it to be 100% of the owner controls width. But this is not the case, and it becomes very evident when the RadDropDownList is used with a template column of a RadGrid. In a RadGrid template column, this setting causes the LIST width to expand all the way to the right edge of the screen. This seems to me to be a bug, as it makes no sense to behave this way. You can see this behavior in the screenshot I have attached. It becomes more evident that this was not the intended functionality (and must be a bug) when you substitute the control with a RadComboBox, having exactly the same attributes. This will use the combo's default settings and show a dropdown list. With the RadCombBox the LIST does not expand to the far right of the screen, it behaves as expected, having 100% of the combobox width. I would expect both controls to work identically with their LISTS when setting the "DropdownWidth" attribute to "100%".
When the LIST is displayed in a RadDropDownList, the datasource is usually a lookup table. Therefore, it is not practical to set the LIST attribute "DropdownWidth" to a fixed number of pixels, since items can be added to the lookup table where the text length is longer than any currently in the table. If you text is too long for the LIST width, the text wraps and this is not a pleasant user experience. This control needs an autosize feature for the LIST, so it fits the longest text without causing wrapping. This feature already exists on the RadComboBox with attributes DropDownAutoWidth="Enabled" and "NoWrap=true". These should also be used I the RadDropDownList so the LISTS work identically.
The issue is not reproducible for RadDropDownList with RenderMode="Lightweight" .
Current style
.k-reset {
margin: 0;
padding: 0;
border: 0;
background: none;
list-style: none; }
What it should be:
.k-reset {
margin: 0;
padding: 0;
border-width: 0;
outline: 0;
text-decoration: none;
font: inherit;
list-style: none
}
Hi Telerik team,
Using DropDownList with 4 items, setting visibility of the third one to false (either directly in apsx definition or setting it at page load event), display is OK, but when selecting the fourth and submitting the changes, server see the third one selected.
Attached is a project reproducing ths issue.
Application Scenario: We have a large page, that we are wanting to improve the performance on. We have a few drop downs that change there available options based on the selections of another drop down. We retrieve the values of the second item though JSON and a generic handler. We generate the items for the drop down list, and then post the final values back when the user is finished. The problem we have is that the user selected item is lost between client and server click actions. I provided a sample scenario that illustrates the problem, and the basic application of this scenario. The drop down does have all the client populated items, but the item that is selected is not retained. Our temporary work around is to store the selected item in a hidden field and read from that which does keep it's value.