Thank you for posting this issue. It seems that this module will better and better.

1. You are right. This is the current behavior. I'm thinking what is right - to create a input elements of the hidden fields or not. What is your think about this?

2. Thank you Fixed. The fix is around the line 69

if( $t.p.colModel[i].hidden===true) { tmp[nm] = $(this).html(); }

replace with

if( $t.p.colModel[i].hidden===true) { tmp[nm] = $(this).html().replace(/\\&nbsp\\;/ig,''); }

Regards

Tony

The Dec. 14th version of jQgrid has cleared up a bunch of issues. Nice work. Thanks!

I have come across a situation where inline edit behaves differently depending on "hidden:true". For reference here is the colModel for that column:

{name:'EntityID',index:'EntityID', hidden:false, width:80,edittype:'text', editable:true, editoptions:{readonly:true,size:4}},

I am adding a row to the grid. I have a few columns that need some initial values so I create a datarow array and call addRowData(-1,datarow,"last").

The EntityID field is getting set using an AutoComplete field event.

With "hidden:false": The following call works:

jQuery("#"+id+"_EntityID","#grid1").val(data[1]);

With "hidden:true": The following call works:

jQuery("#grid1").setRowData(id,{'EntityID':data[1]});

In design we show all the fields. Later when it all works we hide fields. But then that breaks the grid and you don't see that until you do a full test.

I saw one other issue regarding " & n b s p ; " and "hidden:true". This one is easy to explaine, I think. If the column is not set and hidden:true then the post value is "& n b s p ;" However if "hidden:false" then the post value is "" (empty string). In my system they get evaluated differently. The correct value shoud be and empty string. 

Barry