I have integrated the Ignite Ui grid in my application and due to large data set i have turned on "virtualization" with "continuous" mode. And i have a fixed column and some unfixed columns when i scroll down using keyboard down key at some point the grid misaligned the fixed and unfixed rows for a while and then become aligned them after some iterations and this misalignment repeat it self after some iterations until the grid is scrolled to the last row. This issue was mentioned in "known issues and limitation" page of ig grid documentation but there was mentioned that this will produced only in IE 9 and higher version and i am facing this issue in every browser. A workaround was also mentioned there that by setting the " syncRowHeights " property to false in "columnFixing" object and adding some css for rows "td" will resolve the issue but when i set " syncRowHeights " to false and adding the css then misalignment for rows starts even earlier the link for this is issue on known issues and limitation page is "http://www.igniteui.com/help/iggrid-known-issues#misalignment-ie9".
syncRowHeights
Hello Jahanzaib,
I cannot replicate your issue on my side. Do you have a sample which replicates the issue that I can look at? Also can you tell me what is the Ignite UI version that you're using. To get the version execute the following code in your browser's console:
$.ui.igGrid.version
Thanks in advance,Martin PavlovInfragistics, Inc.
Hi Martin,
I have made a test application on Js fiddle. When you scroll it using your keyboard you will see that the rows in fixed column will miss aligned with the rows in unfixed columns after a small interval untill you scrolled to the last row. I am sharing the link below so you can understand the issue and my UI version of ignite is "16.1.20161.2052".
http://jsfiddle.net/jahanzaib_khan/4sz9kn84/12/ (updated link).
Regards,
Jahanzaib
I see. This only reproduces if Virtualization is enabled in combination with Selection and Column Fixing, when scrolling using keyboard down key.
I logged an internal issue with Development ID 223908 about this.
I also created a case on your behalf with number CAS-176395-W3K8P8, so that you can be notified when there is a resolution for the issue.
You can find your active cases under Account - Support Activity in our website. Select your ticket and go to Development Issues tab to view the status of related development issues.
Best regards,Martin PavlovInfragistics, Inc.
Thanks Martin for your quick response. It seems that this issue will be resolved now. I mean that your development team will be providing a new update for this?
I have tried to re produce this issue on angular 2 but unable to reproduce in angular 2 but it is producing in anuglar 1.
Thanks,Jahanzaib