I'm using Virtual Scrolling on the WebDataGrid in Infragistics ASP.Net 2011 Vol 2
This is only effecting Chrome (Version 36.0.1985.125 m). Is working fine in latest version of Firefox, Safari, IE 7, 8, 9 & 10
Here you can see the headings are misaligned with the data (They are supposed to be fixed width at 150px)
When you scroll to the right you can see the data moves quicker than the headings. As you get all the way to the right, the headings gradually grow to the correct size. It's like the total width of the headings is smaller than the total width of the data.
I've removed custom styles and unnecessary features but this is still happening in Chrome only
<igtbl:WebDataGrid ID="uwgDrilldown" runat="server" Width="100%" Height="100%" DefaultColumnWidth="150px"> <Behaviors> <igtbl:VirtualScrolling ThresholdFactor="10" TooltipVisibility="True" AverageRowHeight="29"></igtbl:VirtualScrolling> </Behaviors> </igtbl:WebDataGrid>
Switching on ColumnFixing seems to make it work... but then that feature is causing issues in Internet Explorer where by (upon fixing a column) the first row is the only one that moves to the right. All other rows stay fixed. This is very frustrating!
Any help would be greatly appreciated
I've found that I can enable ColumnFixing to correct the issue I'm having in Chrome. Then I can hide the "FixButtons" to avoid the user from actually fixing a column (which is then avoiding the problem I have in IE). ppffft
<igtbl:WebDataGrid ID="uwgDrilldown" runat="server" Width="100%" Height="100%" DefaultColumnWidth="150px"><Behaviors> <igtbl:ColumnFixing Enabled="true" ShowFixButtons="false"></igtbl:ColumnFixing><igtbl:VirtualScrolling ThresholdFactor="10" TooltipVisibility="True" AverageRowHeight="29"></igtbl:VirtualScrolling></Behaviors></igtbl:WebDataGrid>
Also noticed that if you fix the columns server side it appears to work until you move/sort a column then it breaks in IE again.
This is definitely a clunky work around but hopefully it will help someone else having the same issue.
Hi tomhrvy,
Thanks for posting in our forums!
Thank you for sharing your workaround with the community.
I will look into this and see if I can find a simpler solution for you. I will let you know what I come up with sometime tomorrow.
We just started encountering this problem on all our grids and we are on version 2012.2. It was never happening up until a week or so ago, so it appears the latest version of Chrome has caused it. Look forward to hearing if there is a resolution other than upgrading.