That's a reasonable explanation, though I'm not entirely sure what IE is doing in this case, because poking around with the IE Developer Toolbar on one of the cells gives internal heights of 14 with a 1px border and no padding. Perhaps there are some quirks which even non-quirks mode evades?

 What I might do in that case is to override getDefaultRowHeight, then. I think I might be able to do that by assigning a function to igtbl_Grid.prototype["getDefaultRowHeight"], though I must admit some confusion over how to delay that until the Infragistics JavaScript "classes" are already initialized.

Thanks, Tony

-- Ritchie

 Alrite thanks. that helped.

 I can tell you what I did :)

 I made a function like this:

       function overrideGridRowHeightDetermination() {
          // Override the grid's getDefaultRowHeight which includes 2 extra hardcoded pixels
          igtbl_Grid.prototype["getDefaultRowHeight"] =
            function() {
                var rh = igtbl_parseInt(this.Bands[0].DefaultRowHeight);
                if (!rh)
                    rh = 22;
                return rh;
            }
        }

I included that in one of our .aspx pages that uses the Infragistics grids, and right at the end, in the body, called it:

<script type="text/javascript">overrideGridRowHeightDetermination();</script>

...

You could probably just override it all in one go by just calling the code directly in a <script> area in the body (just before the </body> should work):

 <script type="text/javascript">
igtbl_Grid.prototype["getDefaultRowHeight"] =
function() {
var rh = igtbl_parseInt(this.Bands[0].DefaultRowHeight);
if (!rh)
    rh = 22;
    return rh;
}
</script>

-- Ritchie Annand

Hi Tony,

             Could you please explain me with an example of using proto type to over ride the function, so that it will affect grid on every page ?

 Thanks,

Praveen.

Thanks, Tony! I will remember that for next time. The prototype trick did actually work really well, on top of teaching me a trick or two about JavaScript in the process (I was sure puzzled at first by the giant array of names and functions in ig_WebGrid_dom.js!), but it's probably kinder to override the functions in the client-side event.

Cheers,

-- Ritchie Annand

Ritchie,

You can use the InitializeGrid client-side event to override the JS function. That function is the first thing that fires after the Grid's client-side object is fully built.  You can either do it through the prototype, which will affect every grid on the page, or you can do it through the instance member.  I normally go through the instance, so something like:

function InitializeGrid(id)
{
var grid=igtbl_getGridByID(id);
grid.getDefaultRowHeight=function(){/*insert logic here...*/};
}