Search

@Allan, The Table headings are rendered as a table separate from the data in the grid. This is causing some small but noticeable misalignment with the columns in the Table body.

As noted in the forum rules - link to a test case please. My guess is that your tbody doesn't have the same number of columns as the thead. Allan

THIS }, ] } ] }, "sSearch": "Search all columns:", "sPaginationType": "full_numbers", "aoColumns": col

Most of the rows in your table only have 5 columns. If you fix that it will work just fine: http://live.datatables.net/elixaj/2/edit . DataTables requires that the number of cells === rows * columns. Otherwise it won't work. Allan

The index you are calculating for the column ( $("thead input").index(this) ) isn't taking into account the hidden columns. You want this plug-in for 1.9: http://datatables.net/plug-ins/api#fnVisibleToColumnIndex . 1.10 will have something similar built in (it does already in git :-) ). Allan

and labels using two columns. As a matter of

Currently no - user resizing of columns is not something DataTables is particularly good at just now. Something I will be working on in future (once 1.10 is out and settled a bit). Allan

Ahh, thanks, tangerine! It seems that {"bSortable": false} for all columns and also adding sort listeners via fnSortListener (will the event still be fired? I'm gonna find out) should do the trick ... no?

The 5th parameter ( aiDisplay in this case) reflects the rows, not the columns. The only reflection of the columns in the callback is in the first parameter - the node. Allan

percentage and cumulative percentage columns /* Need to redo the