When the popup elements lack boundary detection e.g.: they don't take into consideration the proximity to the edge.

It would be nice if all dropdown list controls (dropdownlist, radcombobox, etc) had a built-in "x" button somewhere which allowed the user to clear the selection of an item (ie set its selectedIndex to 0).

Clicking on the "x" would also fire the client-side and server-side (if applicable) SelectedIndexChanging and SelectedIndexChanged events.

The control will provide the ability to hover over an image and zoom-in the selected part in a previewer. Such control is available in Google Maps as shown in the attached screenshot Overview-Image-Map-Control.png. Yet another example is displayed in the second screenshot.

You can comment and share your examples or features you would like this control to support.

The multiline textbox should increase its high while the user types, after the currently available space if fulfilled. Like in Facebook "What's on your mind " textbox  

Allow the users to create their own attributes and to be able to work with their client representation after that.

Some times we get customers using the combobox as a show / hide panel for other stuff. While this is some what clever solution, the combo is not really designed for that.

An alternative would be to use the panelbar, yet it does not fit the purpose of the control I have in mind.

Details panel (or what ever name we come up with) is a control that has a title, sort of like the panelbar and content area that's always custom.

The details pane should allow for two modes: overlay and displace e.g. overlay acts as the way combobox acts now and displace acts in a similar fashion to the current panel bar.

Apart from the aforementioned usage, another example will be the configuration panel in the QSF.

In it's current state the RadButton only emulates the looks of a MenuButton, but not the behaviour.

In my point of view, such control should prove valuable to customers. More over, there is a growing need of base controls since we already have a at least three such implementations.

A RadMenuButton should be the base (or it's base should be the base) for all control specific implementations of a menu button