Scroll view incorrect y position when using arrow keys

[Yazid]

Hello,

As the title says. When scrolling through the suggestion list with the arrow keys. After an x number of items they fall out of the scroll view.

Is this something wrong in the suggestion list?

[Selvamani Sankarappan]

Hi Yazid, 

Thanks for Contacting Syncfusion Support, 

We are unable to re-produce the reported issue at our end. We suspect that the issue may be caused due to overriding the external CSS. Please refer the following sample: 

http://www.syncfusion.com/downloads/support/forum/125973/ze/WebApplicationsample-1979821787 

 

If still you face any difficulties, then please revert us by modifying the sample along with the replication procedure in which we can able to reproduce the issue in our end.  

Regards, 

Selvamani S 

[Yazid]

Hi selvamani,

Hi I think the problem is because that some of the suggestions are too long causing them to overflow to two lines.

I think the y position equals the amount of suggestions * size of the first element.

Is there a way to keep showing two lines?

[Selvamani Sankarappan]

Hi Yazid,   

  

Thanks for the update.  

  

When we move the suggestion list items using arrow keys, and if it’s in the hover state, then the list items are not visible. If this is your reported scenario, kindly revert. We will validate this issue and update you with further details. Please refer to the following link:   

http://jsplayground.syncfusion.com/vr5zfjev   

If not, please provide a sample or more details about your issue to re-produce an issue at our end. 

  

Regards,   

Selvamani S.   

[Yazid]

Hi selvamani,

I added some Washington and West Virginia items to the list. If you search for 'w', some items have 1 lines and some have 2 lines causing the scrolling to work incorrectly when using the arrow keys.

Attachment: Untitled_158b7180.zip

[Selvamani Sankarappan]

Hi Yazid,   

  

Thanks for the update.  

 

We were able to re-produce an issue at our end. So, we considered this as a bug and this issue fix will be included in our Volume 3 SP1, 2016 release.    

 

Regards, 

Selvamani S.