DataTables 1.6.2

DataTables CDN files for DataTables 1.6.2. This software was originally released on 2nd March, 2010.

Release notes

A good bug fix version of DataTables this update, and is recommended for anyone using DataTables. Many of the fixes are in obscure places, but there are a few important ones in there. Also worth noting that unless there are any more critical bugs found in this stabilisation release, this will mark the end of the 1.6 series as we start to look towards v1.7.

  • Updated: Now comes with jQuery 1.4.2
  • Fixed: Warning message about number of TD elements got the information in the message the wrong way around!
  • Fixed: State saving was missing 'desc' sorting, due to a bug introduced with the new handling of sorting (aaSorting and asSorting)
  • Fixed: When using full_numbers pagination and jQuery UI, the 'Next' and 'Previous' button had the wrong classes assigned to them, making them look active.
  • Fixed: fnPageChange more or less didn't work as advertised... It does now!
  • Fixed: _fnAddData (internal function used by fnAddData as well as Ajax sourced data) had type detection algorithm wrong (like the fix in 1.6.1)
  • Fixed: fnSetColumnVis now supports nested tables in a DataTable. Could probably do with a rewrite to be more flexible at some point...
  • Fixed: When state saving, and the new table is longer than the old one, DataTables would show an empty table. Now it will roll back to the start
  • Fixed: Auto calculation of column width could be dodgy when considering padding etc. Thanks to 'scottsb' in the forum for this fix (discussion id 1316)
  • Fixed: Sorting classes (in the tbody) could be applied incorrectly when the cell has nested table(s) (forum discussion 1332)
  • Fixed: A small performance increase in the adding of sorting classes due to algorithm change
  • Fixed: Set a default of 'sorting_disabled' for sSortableNone (where sorting has been disabled on a column)
  • Fixed: When attempting to use the pagination buttons which were disabled, DataTables would redraw the table (particularly noticeable with server-side processing). It now won't