We have a combobox declared using the ASP.NET MVC wrapper (2013.2.716).
On IE (10 and earlier), giving it a value upon declaration causes the page to focus on the control and scroll down to it (if the combobox is past the current display area). So we end up with cases where a user would end up seeing the page scrolled down to the middle/bottom. We have confirmed that having ".Suggest(true)" triggers this behavior. Taking it off stops it from happening but we would prefer keeping it as it is helpful to aid users with its auto-completion.
Additionally, we have tested other browsers and they don't exhibit this behavior at all. Is this a known bug?
The declaration is quite simple and looks similar to this:
On IE (10 and earlier), giving it a value upon declaration causes the page to focus on the control and scroll down to it (if the combobox is past the current display area). So we end up with cases where a user would end up seeing the page scrolled down to the middle/bottom. We have confirmed that having ".Suggest(true)" triggers this behavior. Taking it off stops it from happening but we would prefer keeping it as it is helpful to aid users with its auto-completion.
Additionally, we have tested other browsers and they don't exhibit this behavior at all. Is this a known bug?
The declaration is quite simple and looks similar to this:
1.
@Html.Kendo().ComboBox()
2.
.Suggest(true)
3.
.HighlightFirst(true)
4.
.BindTo(dataSource)
5.
.Value("someValue")