DataTables

The plugin is perfect for presenting data grids, data sets and presenting large organized sets of data on a web page.

What is new in this release:

• New API
• Camel case notation
• New stylesheet
• Built-in pagination improvements
• HTML 5 data-* attribute support
• Improved built-in sorting and type detection
• Easier Ajax handling
• Right-to-left layout support

What is new in version 1.10.7:

• New API
• Camel case notation
• New stylesheet
• Built-in pagination improvements
• HTML 5 data-* attribute support
• Improved built-in sorting and type detection
• Easier Ajax handling
• Right-to-left layout support

What is new in version 1.10.5 / 1.10.6-dev:

• New API
• Camel case notation
• New stylesheet
• Built-in pagination improvements
• HTML 5 data-* attribute support
• Improved built-in sorting and type detection
• Easier Ajax handling
• Right-to-left layout support

What is new in version 1.9.3:

• Removed dud CSS from themeroller file.
• Fixed typos in examples/api/multi_filter_select.html.
• Removed duplicate CSS lines.
• Unit test updated for the mData name change from mDataProp. Note that a number of tests to test the backwards compability of mDataProp.
• Removed use of $.browser since this is depricated in jQuery 1.8 and will be completely removed in jQuery 1.9.
• Update examples.

What is new in version 1.9.2:

• Fixes:
• Added jqXHR saving to fnServerData example
• JSDoc syntax errors which were picked up by JSDoc Toolkit
• API: $ method, when used with defered rendering, when all rows have not been rendered, results in jQUery trying to perform a selector on 'null' which throws an error. Now check for the tr having being created before adding it to the array to pass to jQuery
• Use $ and fnUpdate in the index column example
• fnDeleteRow could cause the page to drop back by one
• Calling fnClose in fnPreDrawCallback would result in an error
• Allow custom JUI header and footer classes
• fnStateLoad example has a spare parameter (although not in the parameters list).

What is new in version 1.9.1:

• Update: -webkit0overflow-scrolling:touch on all dataTables_scrollBody CSS files
• DataTables - 1.9.1 release :-)
• Fix unit tests: Witht he change to allow info macros in any of the strings the unit tests need updating to reflect this
• Fix unit test: Number of errors in this test
• New: "destroy" event - when the table is destroyed the destroy event is now triggered. This is very similar to how aoDestroyCallback worked before, but this brings the implementation into line with the newer callback/events mechanisim used in DataTable
• Update: Update the text for the two jEditable examples
• New: Column option "sCellType" - allows you to create TD (default) or TH cells for a column. Useful for creating row headings in the TBODY.
• New: Static API method - fnVersionCheck same as the version check that is already available as an instance method, but here available as a static API method attached to $.fn.dataTable
• New: Static API method - fnIsDataTable - check if a TABLE node is a DataTable or not
• New: Static API method - fnTables - get the DataTables that are initialised on the table (optionally limit to just the visible tables)
• Fix: Scrollbody height in IE7- - use offsetHeight consistently - 9424
• API - fix: The parameter for fnDraw was inverted by mistake in the 1.9.0 release - 7825
• Dev fix: Missed a variable def in the recent _fnLanguageCompat change
• Docs - fix: Show oSettings parameter in fnDrawCallback example - 9067
• Docs - fix: Typos
• Docs - fix: fnSort documentation updated to indicate column sorting - 9094
• Fix: afnSortData functions were not being executed with the DataTables instance's scope

What is new in version 1.9.0:

• DataTables 1.9 has a much improved API for state customisation, but it has meant removing the old parameters fnStateLoadCallback and fnStateSaveCallback.

What is new in version 1.8.2:

• Fix: Unit test compatibility fix for IE7
• New: If a data source is found to be a function, then the function is executed and the return used for the cell display (+sorting, filtering etc). This is useful for integration with knockout.js and backbone.js etc.
• New: All examples which show Ajax requests now show the JSON response from the server (highlighted to be readiable JSON formatting) and the responses shown will update with each additional request. The idea is to make the formatting that DataTables expects / can cope with more obvious
• Dev fix: The new custom events will always pass the DataTables settings object as the first parameter
• Update to latest jQuery - 1.6.3

What is new in version 1.8.1:

• Dev fix: fnDestry wasn't reapplying original with correctly due to a mistake in an earlier commit - picked up by unit tests
• Fix: Row alignment with x-scrolling disabled and the table too small to draw fully. Previously DataTables would emit an error about the columns not aligning in this case, and then try its best to draw the table, but this would end up looking quite bad. The fix is to not allow the table to draw smaller than it can possibly be when x-scrolling is disabled. This effects dynamically resizable tables - 5232
• Update: For objects, consider mDataProp which is sent from DataTables for sorting and filtering to get the correct order of the rows. This is useful for ColReorder and more generally it increases the flexability of the whole table
• New: Send mDataProp to the server for server-side processing. This is very simialr to the sNames parameter, but more convient when already using mDataProp
• Updated: Update to latest jQuery - 1.6.1
• Fix: Columns which are sortable but hidden have events attached to them for sorting, but this event handler is not removed when the column is made visible again for fnDestroy. Simply need to change the order of how the destroy is done - i.e. remove events just after the columns are made visible, not before - 5497
• Fix: When complex expressions are built up with aoColumnDefs, resulting in the ability for a column to be turned "on and off" during initialisation, it would result in the column classes possibly not being correct for the sorting - 5472 - kudos to rups for this fix
• New: Accessability features - the length changing control and filtering control are now wrapped in <label> tags (an explicit relationship to their input elements) to aid accessability. You can see this immediately by simply clicking on the "Search:" text now - it will focus the input of the text box, while for screen readers it will give the label text from the label.
• New: The filtering input language string (oLanguage.sSearch) now has the "macro" _INPUT_ in it to allow the input element to be positioned anywhere in the string. For example if you gave "sSearch": "Data_INPUT_Tables" the output for the filter would be "Data<input.../>Tables". This is optional - if _INPUT_ is not given, then as before will will tack the input element on to the end of the given (or default) text string.
• Fix: The ability to use complex data structures in 1.8 means that arrays which are passed into to fnUpdate need not strictly be the same length as the number of columns in the table - therefore the warning that is given if you do this is wrong... no other code changes needed - just no need to generate the warning! Unit test added - 5396
• Examples fix: Details table has one extra column in it at the start, so this needs to be taken into account when sorting - 5422
• Fix: The table width is not set when auto width is disabled so we should not set it when destroying the table - 5220
• Start DataTables 1.8.1 development
• Fix: A couple of typos in the examples

What is new in version 1.7.5:

• Fixed: fnInitComplete was not the last thing to be executed when using DOM source. IT was possible that you could set sAjaxSource in fnInitComplete which would then trigger DataTables to do an Ajax call incorrectly.
• Updated: Reliability of unit tests in non-webkit browsers
• Fixed: fnDrawCallback was actually the first of the draw callback functions that was called (the internal callbacks were called later). This was incorrect and we now loop over the array to get the order we want. At some point in future it might be required to have an ordering if these draw callbacks become interdependant.
• Performance: Re-written the sorting implementation so it doesn't use either eval() of $.inArray(). inArray was found to have a serious negative effect on IE which counts operations to give the 'script is running slow' error message - the new implemention uses a value / key reverse mapping to make the look up as fast as a single object parameter retreival. Furthermore, I've done some optimisation and feature completeness work on the non-eval version of the sorting (previously the AIR sorting method) and I've found this to be at least as good (faster in some cases) than the old eval() sort, so this is now the default and only sorting method DataTables provides - 2922
• Merge branch 'master' of github.com:DataTables/DataTables
• Updated: fnAdjustColumnSizing when called with 'false' as the first (and only) parameter will now apply the calculated column sizes to the table when scrolling is being used. This allows a non-Ajax update to occur if using server-side processing. Thanks to Cat Weismann for this patch.
• Updated: fnAdjustColumnSizing when called with 'false' as the first (and only) parameter will now apply the calculated column sizes to the table when scrolling is being used. This allows a non-Ajax update to occur if using server-side processing.
• Fixed: The behaviour for complex headers has been altered slightly for complex headers in that only the first of non-unique TH elements will be click to sort-able. Unit test update needed as this is different behaviour from before when all elements belonging to a column were click to sort.
• Updated - now using jQuery 1.4.4 as the copy of jQuery included in the DataTables distribution. Passes all unit tests
• Fixed: When using server-side processing and having called fnDestroy, don't make another XHR to the server as the data won't be used - 3375
• Fix: Correctly add the sClass to the TH elements in the header
• New: Add bScrollAutoCss option (default true). This allows you to control the scrolling styles with CSS, where as normally DataTables will set (and override) the styles itself. This is useful for if you want to have a scroll bar showing at all times (normally auto).
• Fixed: Remove bold styling when using JUI as it looks out of place in the table controls
• New: Column visibility options in DataTables (bVisible and fnSetColumnVis) now take into account more than one row in THEAD and TFOOT. Please note that colspan and rowspan are NOT supported when using column visibility options in the header and footer, and will very likely have effects which are not at all desirable. As such there are conditions on this use (note that if you only have one row in the header / footer, then this has no impact), specifically the number of cells in the header / footer much be equal to the columns * rows (in each one). This way DataTables can accurately add and remove the cells as needed. The cells may be either TH or TD elements, but DataTables still requires at least one TH element for each column.
• Updated: Previously when multiple cells were detected as unique to a column the last one would be given priority (i.e. sorting event handler etc). This is now no longer the case and the first will take priority.
• Fixed: Remove the 'sNames' parameter that was introduced for server-side processing in 1.7.4. The parameter 'sColumns' actually performs exactly this task already. Doh. Also update the example PHP to take this into account - 3218

Requirements:

• JavaScript enabled on client side
• jQuery