Hi,
I've got an issue where the RadGrid is hiding columns that it shouldn't do when Google Chrome has hardware acceleration disabled. We're not seeing the same behaviour on Edge or Internet Explorer, and it doesn't seem to happen every time.
I'm trying to work around it in JavaScript by raising RadAjaxManager.ajaxRequestWithTarget and raising the scroll event, but this just duplicates columns.
Can you give me a bit of guidance how to work round this?
Thanks
6 Answers, 1 is accepted

Hi Simon,
One of the most common scenarios that results in the behavior you have described is when the Frozen Columns functionality is enabled. If that is the case, the way the grid handles this functionality is by showing/hiding columns on client-side. Please note, that having hidden columns using set by the Display property is not supported with this scenario. See Known Limitations - Frozen Columns
In case your scenario is different from the one described above, we would require more information so that we can test it locally. Sharing the markup and client/server side code related to the grid would be very helpful.
Kind regards,
Attila Antal
Progress Telerik

Hi Attila,
In our scenario, all of the columns are visible at all times. There is a brief flash of the columns that aren't frozen, and then they disappear again. We do have a workaround, which is to resize the window, and that makes them reappear.
As I say, this is a bug that seems to affect Chrome when hardware acceleration is turned off,and only in certain circumstances. I haven't been able to create a project that recreates the issue either, as yet, so I think I am probably going to try and work out how to raise this as a Chrome issue as it is starting to feel more like their problem - browser rendering should be consistent with and without hardware acceleration, and this issue doesn't affect Edge, Internet Explorer or (as far as I can tell) Firefox.
Hi Simon,
I assume you are right about the bug, but we need to confirm it first. For that we would need the steps/instructions that will help us replicate the issue. Once we have the issue running locally, we would be able to tell whether it's a bug of the control/browser related or is just due to bad configuration.
Please send us the steps to replicate the issue or send us a runnable sample project and we'll look into this.
I look forward to hearing from you.
Kind regards,
Attila Antal
Progress Telerik

Hi Simon,
Very good! We'll work on that and once we figure out the issue and solution, we will share the results in this Forum thread as well.
Kind regards,
Attila Antal
Progress Telerik