EasyUI Forum

General Category => Bug Report => Topic started by: chandrasigniant on January 09, 2017, 02:15:11 PM



Title: Scrolling the selected row into view has a bug
Post by: chandrasigniant on January 09, 2017, 02:15:11 PM
When there is scrollbar on a treegrid and select the last row, it shifts the last row upward and partly shows the row below that.
In normal cases it is ok. But when we added double click feature to the rows, the row below the selected row is being selected when we double click the last row (especially when the second half of the rows being selected is used as double click area).
On your Demo pages of treegrid (http://www.jeasyui.com/demo/main/index.php?plugin=TreeGrid&theme=default&dir=ltr&pitem=) this can be reproduced using Dynamic Loading in TreeGrid example.

Can you fix it please?


Title: Re: Scrolling the selected row into view has a bug
Post by: jarry on January 09, 2017, 07:32:51 PM
Please try to download the patch from http://www.jeasyui.com/download/downloads/jquery-easyui-1.5.1-patch.zip.


Title: Re: Scrolling the selected row into view has a bug
Post by: chandrasigniant on January 10, 2017, 01:20:49 PM
Still the same issue, this is reproducible only when the grid has vertical scrollbar visible (more rows below the last row being  selected).
The last row when fully visible should not bring jump upwards ideally and need not bring the row below it partially into the view


Title: Re: Scrolling the selected row into view has a bug
Post by: jarry on January 10, 2017, 07:05:43 PM
Selecting a row will scroll to this row to make it visible. If you don't want this feature, please set the 'scrollOnSelect' property to false. Make sure to download the patch from http://www.jeasyui.com/download/downloads/jquery-easyui-1.5.1-patch.zip


Title: Re: Scrolling the selected row into view has a bug
Post by: chandrasigniant on January 11, 2017, 03:37:47 PM
scrolling the selected row into view is ok, but why does it have to bring the node below it partially into view ?
That is the problem I am facing, because the double click on that selected node is getting triggered on the node below it.