Thanks for this. Will look definitley at this. Trying to google it seems that there is a bug in WebKit (but only comments, no clear explain). I will try to investigate the problem deeper.

Best Regards

Tony

In the hope I'm not posting the same bug, I did search for something simliar but didn't find antyhing. I downloaded the latest code about 2 weeks ago and only recently made Chrome the primary browser for my app.  There appears to be a problem in the getRowData function that is very wierd. Works for some pages in Chrome, but not in the particular page I'm having an issue with.

To "fix" (don't know if i can call it a fix) it, we removed the use of javascript's namedItem function and replaced it with a JQuery equavilent like so:

getRowData : function( rowid ) {
        var res = {};
        this.each(function(){
            var $t = this,nm,ind;
            //ind = $t.rows.namedItem(rowid);
            ind=$('#'+rowid);
            if (ind.length==0) return res;
            //if(!ind) return res;
            //if (ind.length!=undefined) ind=ind[0];           
            $('td',ind[0]).each( function(i) {
                nm = $t.p.colModel[i].name;
                if ( nm !== 'cb' && nm !== 'subgrid') {
                    if($t.p.treeGrid===true && nm == $t.p.ExpandColumn) {
                        res[nm] = $.jgrid.htmlDecode($("span:first",this).html());
                    } else {
                        res[nm] = $.jgrid.htmlDecode($(this).html());
                    }
                }
            });
        });
        return res;
    }

What we don't understand is why namedItem would return an Element in one case and a NodeList in another? Perhaps you have an idea of why it is doing this? Like I said, similar code works on other pages in Chrome... so it's kinda wierd in a way.

Regards,

Roger