Update:

Hello everyone,

The Chrome clearly had a regression in their rendering engine as with the latest beta build [ Chrome Version 63.0.3239.18 (Official Build) beta (64-bit) ] the issue is no longer

present for the data grid. Unfortunately the release data for the official Chrome 63 release is around December 5th 2017.

We do have a fix but we're still debating whether to include it in the codebase as this is clearly a 3rd party issue [one browser, one specific version] which will be fixed in the next official release of the browser.

As it seems the CSS workaround does not cover 100% of the cases here is another one would force the browser to re-render the DOM structure of the grid.

1. Add a client-side event handler for the WebDataGrid Initialize event:

<ig:WebDataGrid ClientEvents-Initialize="[your_handler_name]"></ig:WebDataGrid>

2. Inside the event handler force the browser to re-render the grid by changing one of the CSS properties of the main table element.

IMO Chrome will repaint the DOM even if you change something as trivial as the color/font-size of the table element but in the example below we target the table visibility.

Your handler should be something like that:

<script>

function your_handler_here(sender, args) {
    sender._elements.dataTbl.style = "visible";
    sender._elements.dataTbl.style = "inherit";
}

</script>

In case you already have an event handler on the Initialize event just add those lines somewhere in your existing handler.

I'll monitor this thread and if neither of the workarounds work for you please post here.

This almost worked for me. 

I've added the event ob the server side:

myGrid.ClientEvents.Initialize = "ChromeFix";

Then, I had to change the event-handler to

function ChromeFix(sender, args) {
sender._elements.dataTbl.style.visibility = "visible";
sender._elements.header.style.visibility = "visible";
}

HTH someone.