I could test the last changed in grid.base.js. Everything seems be fixed now.

On the other side the code of grid.filter.js has some small problems with selects build from dataUrl. If the select has no option with selected=”selected” attribute the old plugin jquery.searchFilter.js shown just the first option as selected.

Try with the old style demo and the new filter demo. The old plugin worked without any problem with selects.

The new plugin looks different in FF and IE. In FF one see

and on IE and Chrome:

but after the click on the select box:

Moreover in many places of the code of grid.common.js one find code like

this.selected = “”

or

this.selected= “selected”;

or

ov.selected =”selected”;

where this or ov are DOM elements of the . The selected property of the DOM element is boolean and readonly (see here for example) and not string. One should probably

Hi Tony!

I like that you think in the same direction as I am. I thought also about custom cell/column properties, but want not do too large changes because I don't known your opinion about this. Moreover the current implementatin of jqGrid has already implementation of the title attribute and it work even with custom formatters. So from the aspect of compatibility with the existing code I thought to implement first of all a solution for the title attribute and then suggest some more general solution for any attributes or properties.

It is important to define which properties can be used by the general custom properties. For example it should be clear for the developer which use jqGrid how all work if he use for example class property for the column in the colModel and use new custom way which ovewrite the property. I mean that itwould be nice to have less paremeters in colModel and have less situation when one colModel property ovewrite the other property. Nevertheless I think that one can solve the problem or at least include the corresponding part in the documentation. So I think that one general way to set any attribute or property of the column (cells of the column) would be the best way.

A general way for custom classes like changes of color or background color is very typical requirement. In the way one can reduce the requirement to write custom formatter for the date for example if one only need to change the color of some dates.

I am glad, that you like the idea.

Best regards
Oleg

P.S. I have some ideas about functions like dataInit and dataEvents used for the column at the end of grid loaging process (before loadComplete). The main idea is to fill the grid data as text in gridview:true mode, and then make some initializations after interting the text on the page. So one could make some work with DOM elemnts of grid. It could reduce the usage afterInsertRow in the most cases and makting some bindings. In the way one can use unobtrusive style of links or use some custom controls like raty plugin see the demo.

The main implementation idea is to use selectors like in the answer. It would be better that I describe all more exactly in the next post. I will try to do this today or tomorrow.

Hi Tony,

It seems to me that all construction from compareFnMap where not() are used ('nc', 'bn', 'en', 'ni') work incrrect with OR ('any') operation. Try for example in “fixed” the demo for

(Client “does not end with” 'F') OR (Client “does not end with” 'O')

or (Client “does not contain” 'F') OR (Client “does not contain” 'O').

It will executed as

(Client “does not end with” 'F') AND (Client “does not end with” 'O')

or as (Client “does not contain” 'F') AND (Client “does not contain” 'O') instead.

I am not sure that the order of operators in compareFnMap correct is or probebly one have to insert call of _resetNegate() somewhere. It can be that one should modify this.orNot and this.andNot to use

this.andNot=function(f,v,x){