DropdownList scrollbars and DropdownHeight

4 posts, 0 answers
  1. Albert Shenker
    Albert Shenker avatar
    550 posts
    Member since:
    Mar 2004

    Posted 24 Sep 2014 Link to this post

    Contrary to what I mentioned in this thread...

    http://www.telerik.com/forums/missing-dropdown-scrollbar#VJvAA0Py9kitURlSmCO7iw

    It would appear that the Dropdownlist control suffers from the same issue of not displaying scrollbars and calculating its height from available screen space (a la radcomobox) without explicitly setting a DropDownHeight property. Why is this so? It doesn't make any sense.
  2. Nencho
    Admin
    Nencho avatar
    1457 posts

    Posted 29 Sep 2014 Link to this post

    Hello Albert,

    Actually there is already a logged feature request for implementation of such functionality. I would suggest you to vote for it in the link below:

    http://feedback.telerik.com/Project/108/Feedback/Details/46275-add-raddropdownlist-screen-boundary-detection


    Regards,
    Nencho
    Telerik
     

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

     
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Albert Shenker
    Albert Shenker avatar
    550 posts
    Member since:
    Mar 2004

    Posted 29 Sep 2014 in reply to Nencho Link to this post

    Am I to understand it is Telerik's policy that obvious deficiencies in their products, which they are fully aware of, will not be addressed until some magical number of users happen to stumble upon a feature request link and go to the trouble of voting for it?

    Why must users be required to request features that should have been implemented in the first place? I keep asking this question over and over again, particularly with regards to poorly executed controls, like RadDropdownList, and no one from Telerik seems capable of providing a good answer. I'm guessing your developers are all too busy designing yet another monstrous platform to be bothered to make sure your flagship products remain high quality.
  5. Marin Bratanov
    Admin
    Marin Bratanov avatar
    3599 posts

    Posted 02 Oct 2014 Link to this post

    Hello Albert,

    As we have already discussed a number of times, not all features can be built-in the controls, especially off the bat. There are various reasons for that. Let's name a few:

    • We cannot know exactly which will be the most popular features before we get feedback from our clients. Ultimately, we try to satisfy as many people as possible, so we need to choose features with greater impact in most cases.
    • Some features are more time consuming than others and sometimes implementing a couple of other features is chosen over implementing a single one.
    • Some things are easily achieved by the developers via a few lines of CSS or script, so creating built-in features or properties for every single scenario is not possible. This will greatly bloat the code and add unnecessary complexity to it.
    • Not all people have the same view on each case. There are issues that seem critical to some, but are irrelevant to many, and vice versa. This is an extremely important reason why we gather feedback to help evaluate an issue's priority and impact.

    On gathering feedback - we do have various channels and the feedback portal is our primary one. When an idea is added there it provides an easy way to track it so you do not need to keep asking whether it is implemented or what is its status - you can get automated email notifications.

    Please let me know if you have outstanding questions.


    Regards,

    Marin Bratanov
    Telerik
     

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

     
Back to Top