DataTables

Release comments

It is worth noting that I've put in new algorithms for parts of DataTables, so there is the potential that things might break (as with all new software releases). 1.6.1 passes clean through my unit tests, but if you do spot anything, please do jump into the forum and let me know!

Release notes

• Updated: fnOpen now returns the TR node that was created

• Fixed: Cookie contents were not escaped. As a return ';' and other characters could cause issues.
• Fixed: Type detection was incorrectly only looking at the first row (under certain circumstances).
• Fixed: Type detection could get confused if a column contained (only) date and numeric information.
• Fixed: If asSorting was defined (but not aaSorting) then we should use the first sorting option for a column in asSorting rather than the default.
• Fixed: The examples index in the distribution had a few wrong links in it

• Optimisation: Sorting classes (bSortClasses) was very slow when removing previously assigned classes. An optimisation for this as reduced initialisation time for large data sets by up to 90%!
  • - Test set, 500 rows with 9 columns
  • - Safari 4 - 4500mS to 400mS
  • - Firefox 3.5 - 2500mS to 600mS
  • - IE 8 - 'Unresponsive script' to 1500mS
• Optimisation 2: Not quite happy with the sorting classes still, so removed the use of jQuery's removeClass and selector to do direct DOM manipulation. We can do this here since we directly control the table and "know" it's structure ahead of time.
  • - Test set, 2000 rows with 9 columns
  • - Safari 4 - 1500mS to 300mS
  • - Firefox 3.5 - 1100mS to 370mS
  • - IE8 - 'Unresponsive script' to 600mS
• Optimisation: Sorting classes (bSortClasses) was slow when adding the required sorting classes. Using direct DOM manipulation the draw has be substantially improved:
  • - Test set, 2000 rows with 9 columns
  • - Safari 4 - 2200mS to 1100mS
  • - Firefox 3.5 - 2800mS to 2100mS
  • - IE8 - 'Unresponsive script' to 10300mS
• Optimisation: Fixed table width (required so pagination doesn't have a chance to cause the table width to 'jump') is now done at the end of the first draw. The advantage of this is that the browser need only 'size' the table with the initial number of DataTables rows (10 by default) rather than the unenhanced table (2000 rows in this test)
  • - Test set, 2000 rows with 9 columns
  • - Safari 4 - 1100mS to 660mS
  • - Firefox 3.5 - 2100mS to 1500mS
  • - IE8 - 10300mS to 3100mS
• Optimisation: Very minor (but welcome all the same) draw time speed up by altering the algorithm for removing and then adding rows
  • - Test set, 57 rows with 5 columns, draw 100 rows and then 10, looped 1000 times
  • - Safari 4 - 2000mS to 1800mS
  • - Firefox 3.5 - 11000mS to 9600mS
  • - IE8 - not tested
• Optimisation: Change method for reading in the data from the DOM for _fnGatherData.
  • - Test set, 2000 rows with 9 columns
  • - Safari 4 - 550mS to 440mS
  • - Firefox 3.5 - 1300mS to 1000mS
  • - IE8 - 4100mS to 3500mS

Release comments

Enjoy!

Release notes

• New: fnVersionCheck API function which can be used by plug-ins to check if DataTables is at a suitable version for them to be supported
• New: fnPageChange API function. This is to simplify paging, both internally and externally.
• New: Now ships with jQuery 1.4 in the package
• New: A warning is alert()ed when you try to re-initialise a table now as this is unsupported behaviour. Use the API to make any required changes. This is basically a sanity check
• New: KeyTable is now included in the DataTables distribution (under the extras directory)
• New: ReadMe in the extra directory explaining the various plug-ins
• New: fnDeleteRow, fnUpdate and fnGetData now accept either an aoData index, or the TR element as the target parameter (aoData index was required before, which required looking up the position before calling either of these functions).

• Fixed: The 'alert' errors that DataTables gives have been modified to clearly indicate that they come from DataTables
• Fixed: DataTables and it's content could "disappear" in IE7/8 due to the position:relative on .dataTables_wrapper. Adding zoom:1 fixes this. With special thanks to Tobias Bathge for his kind assistance with this!
• Fixed: api/row_details.html, api/select_single_row.html, server_side/row_details.html example shows the new use of fnGetData with a TR element being passed. Clear and easier to understand.
• Fixed: server_side/select_rows.html had a memory leak in it. Now uses $.live() event handler and the updated syntax for fnGetData
• Fixed: The sorting icons are now png8 files, with transparent backgrounds. Suitable for easier integration. The source psd is also included
• Fixed: Paging plug-in example updated for the new pagination API in DataTables 1.6
• Fixed: Initialisation of aaSorting, could result in poor interaction behaviour if not used in combination with aoColumns.asSorting (e.g. double click required to reverse sorting). Now automatically initialised to the correct sorting interaction order.
• Fixed: There was an extraneous call to _fnSortingClasses (which is quite a heavy function) in _fnInitalise
• Fixed: Removed instances of iSortDir_ in the code examples to match the API change
• Fixed: Plug-ins are given their own section in the 'examples'

Release comments

So what are the major features you expect in 1.6? Nothing revolutionary, but certainly evolutionary:

• Support for multiple instances of sDom elements. What this means is that you can have two (or more!) filter boxes, pagination elements or any other table control!v
• Stable sorting. Particularly important in Google Chrome, the table will retain it's original sorting order if items match value.
• A bit more speed :-)

Note that there have been a few API changes so you will have to make changes to use DataTables 1.6 if you use:

• Server-side processing: iSortDir_{x} has been renamed to sSortDir_{x} to reflect that it's a string
• A custom pagination plug-in: The fnInit function now takes three arguments. Please see the release notes.

Also note that the current releases of TableTools and FixedHeader are not currently compatible with 1.6.beta. New versions will be available soon.

As always, feedback is most welcome - please post any bugs and comments in the forum. Also, please remember to make a donation if you are using and enjoying DataTables :-)

1.6.beta examples

Release notes

• API Change: Server-side processing, iSortDir_{x} changed to sSortDir_{x}
• API Change: Pagination plug-ins: fnInit now takes three arguments: 1. settings object, 2. container node, 3, draw callback function. The insertion of 2. is new.
• API Change: Plug-ins are no longer required to return a node (using sDom features). Features can now be added in this way for Javascript only functions as well.
• API Change: oSettings.fnDrawCallback has been renamed oSettings.aoDrawCallback and is now an array of objects with parameters 'fn' and 'sName'. No external change needed unless you are developing plug-ins
• New: Stable sorting - the original order is maintained when rows match (when the value is checked for sorting). This is particularly noticeable in Google Chrome)
• New: fnServerData can now be used to modify the Ajax data pull, in exactly the same way as it can be for server-side processing
• Fixed: Now fully pass jslint - no warnings
• Fixed: Column sorting classes would be applied on the server-side when bSortClasses was false
• Fixed: fnAddData will simply ignore an empty array that is passed into it
• Changed: Code ordering - now grouped into features
• Changed: Draw speed is increased through improved row striping. aoData._sRowStripe is a new internal variable for tracking this
• Changed: Due to the option of multiple instances of a 'feature' in sDom, the ID attributes are applied only to the first instance of a new element (for example the information div). It is recommended that classes are used for styling.
• To do: The beta will break TableTools and FixedHeader

Release comments

Release notes

• Fixed: sDom issues in IE

Release comments

Release notes

• New: Two new sDom constants: H and F for jQuery UI theme header and footer (a long string of classes). Done like this to allow easier accessibility of sDom when used with jQueryUI theming
• New: bSortable_{i} and bSearchable_{i} have been added as parameters sent to the server-side (when server-side processing is used). This allows for the client and server-sides to be more flexible

• Updated: jEditable demo now has IDs in the TD elements which are also submitted.

• Fixed: iCookieDuration was missing from the initialisation parameters
• Fixed: State saving did not restore pagination state when bFilter was false
• Fixed: When sorting disabled (either by an individual column, or globally with bSort) classes were not applied to the table header cells, resulting in a poor visual effect, particularly with jQuery UI themeing enabled
• Fixed: When sName defined for the column but sColumns not returned by the server, there would be a Javascript error

Release comments

Of these new features, the biggest is a new API for sorting, which allows a table to be sorted based on live information in the DOM - an example is worth a thousand words. Also two flags have been added to the DataTables settings object which are used to indicate if either filtering or sorting have been applied in the latest redraw, allowing you to take appropriate actions: for example updating an index column.

Release notes

• New: New API for sorting data (specifically indented for DOM variable data such as form elements)
• New: Filtering and sorting are now (individually) flagged has having occurred, when appropriate, such that fnDrawCallback can be used as a hook when sorting and/or filtering has occurred. The new parameters are in oSettings as bSorted and bFiltered.
• New: Example - api/counter_column.html
• New: Example - api/dom_sorting.html

• Updated: Documentation updated for new sorting API and example data source sorting functions added to plug-ins page.

• Fixed: jQuery classes were not applied to thead elements which had sorting disabled on them

Release comments

Release notes

• New: Default sorting direction is now controllable
• New: You can limit sorting to a single direction, or add complex behaviour as required
• New: fnRender object now also included oSettings
• New: fnDraw API function now accepts a single argument (boolean) to indicate if the redraw should be complete (i.e. re-sort and re-filter), which has the side effect of resetting the pagination, or just update the display as it is.

• Updated: The jQuery UI classes for sorting have been updated to take account of the new sorting direction control feature. This involves the use of a mix of triangle and chevron icons to make it clear what sorting can be controlled.

• Fixed: If the auto width calculation has found a table width of 0, it is not applied to the table. The reason being is that this can occur when the table is not in the documents, display flow.
• Fixed: Pressing return in the search box could cause a form to be submitted
• Fixed: JUI themes: insert span for the sorting direction in the header as the first element in the TH - makes it suitable for display:block styling. Thanks to TomC for this fix
• Fixed: fnOpen() will now work for elements which are not on the current page.
• Fixed: Child-tables could cause issues with the width calculation were to many TD elements were being selected
• Fixed: Selectors checked and improved for dealing with child-tables
• Fixed: When changing the number of columns in a table, and having bStateSave enabled, this could cause DataTables to expect the wrong number of columns. Now it will expect what is in the data source, and throw away the state information if it is out of date.
• Fixed: When showing all records (-1 length) the 'Next' and 'Previous' buttons weren't being disabled
• Fixed: When showing all records (-1 length) some of the buttons could cause 'odd' behaviour when clicked, even although nothing should have happened
• Fixed: _fnReDraw was missing from oApi
• Fixed: Adding a column to an empty table element with the column initially hidden and then shown would result in the column title failing to be to displayed (the cell would be)

Release comments

Release notes

• New: Full support for jQuery UI's Theme Roller (using the bJQueryUI initialisation parameter)
• New: Custom classes names for all elements can now be defined
• New: In full numbers paging, the 'permanent' buttons (first, next etc) now have their classes updated to be 'active' when they can be clicked on.

• Fixed: When using sAjaxSource with state saving, the paginging number was not retained
• Fixed: Internal naming for 'first' span for full_numbers paging was incorrect
• Fixed: _fnGetTrNodes, _fnGetDataMaster and fnGetPosition did not consider nulls in aoData (as a result of fnDelete)
• Fixed: Column detection did not take account of TD elements mixed in with the THs

Release comments

Release notes

• Fixed: full_numbers paging had a 'funny' in the page count
• Fixed: Fields could be incorrectly detected as 'date' if the browser sees null as a number (isNaN)
• Fixed: Unique TD detection was broken by a "fix" in 1.5.0. This has now been properly fixed
• Fixed: Showing and hiding columns could break the table formatting if there are any 'open' rows
• Fixed: Pressing enter in the filtering input could cause form submission
• Fixed: Processing display could be left as 'on' once initialisation has completed if using bProcessing without AjaxSource

Release comments

Release notes

• Summary of major changes since 1.4
• New: Server-side processing for handing of the processing of large data sets to a database. Also allows for Gear and AIR database support.
• New: New plug-in support for custom filtering
• New: Unit test framework with 1'300+ tests
• New: Full support for Adobe AIR
• New: Many new examples show casing the power of DataTables
• Fixed: Plenty of bugs!

• Minor changes since 1.5 beta 11
• Updated: Now ships with jQuery 1.3.2
• Fixed: Parsing data from JS array which contained data other than strings was broken
• Fixed: If bProcessing is set to true then it is now also used during initialisation for DOM and JS array sourced data (previously it was only effective during initialisation for server-side or ajax data).
• Fixed: Unique TD detection could be incorrect due to a dodgy loop
• Fixed: Alternative paging could get into funny states when used with length changing

Release comments

Release notes

• Updated: When using aoSearchCols (initialisation variable for column searching) it is now possible to use null for columns where you just want to use the default (no filter), and also bEscapeRegex is no longer mandatory in the object (if not given, it will default to true).

• Fixed: tfoot elements are removed as needed by the hidden columns. Demos updated.
• Fixed: Case where no info element given in sDom, but info feature enabled would cause a JS error
• Fixed: Case where no paging element given in sDom, but paging feature enabled would cause a JS error
• Fixed: Server-side processing - when pagination is disabled, DataTables will send -1 was the length to display, to allow the script to not include the limit option in the SQL statement.
• Fixed: Server-side processing - when sorting is feature disabled, sorting information is not sent to the server
• Fixed: Server-side processing - when filtering is feature disabled, filtering information is not sent to the server
• Fixed: Server-side processing - fnHeaderCallback and fnFooterCallback's 4th argument (end draw index) was incorrect.
• Fixed: When filtering language string is empty, a single space is no longer automatically inserted before the filtering input
• Fixed: Column names could be set to '' (blank) when using aaData as the data source.
• Fixed: Ajax source - IE could throw an error when dealing with an empty table

Release comments

Release notes

• Updated: A number of optimisations for the SQL in the server-side processing scripts. Provides a significant improvement for large data sets.

• Fixed: Server-side processing requests could get out of order if a later request took a very short amount of time to complete, while earlier ones took a long time. To fix this "sEcho" is sent as a parameter to the server side, and it is expected that this will be returned to the client. This is not mandatory but is STRONGLY RECOMMENDED.
• Fixed: Server-side processing pipelining example updated for new sEcho parameter
• Fixed: A whole bunch of little optimisations based on jslint information - many thanks to Oskar Gewalli for the work on this and the diff file!
• Fixed: A small change to how the filter value is set on initialisation to take account of the back button and webkit browsers
• Fixed: The header for the JS files now points to www.datatables.net for more information about DataTables
• Fixed: JSON return from server-side is now strict JSON valid
• Fixed: In full numbers paging, the correct IDs weren't being applied to the required elements.
• Fixed: An empty array for asStripClasses could cause issues in WebKit based browsers
• Fixed: State saving now includes column visibility (due to API interaction) - I would strongly recommend using bAutoWidth:false and setting the column widths yourself if using this at the moment. Reason being that DataTables doesn't use hidden columns for calculating the width of the table.

Release comments

Release notes

• New: Added $.fn.dataTableExt.sVersion with the version string
• New: Added $.fn.dataTableExt.aoFeatures for adding new features to DataTables view API and in-combination with sDom.
• New: Added $.fn.dataTableExt.ofnSearch for custom formatting of filtering based on type
• New: oApi is now referenced in oSettings - as such it is easier to perform functions where ever oSettings is available
• New: fnAddData and other row manipulations (server callback, Ajax source etc) will now give an alert error whenever a row is found which does not match the row length to the columns

• Updated: Internal referencing to the $.fn.dataTableExt object should be a lot faster now

• Fixed: Processing display was prematurely removed when using server-side processing and sorting on columns
• Fixed: When fnRowCallback doesn't return a node an alert is now given
• Fixed: Events in the header were cancelled prematurely in Safari. This was due to efforts to prevent text selection with multi-column sorting.
• Fixed: Fast paging with two_buttons in Safari could cause text selection which looked very ugly.
• Fixed: Click event handlers are not added to TH elements for columns which are not sortable

Release comments

Release notes

• New: When working with multiple tables from a single initialisation call, you can now use $.fn.dataTableExt.iApiIndex to tell the API functions which table to use.
• New: fnDeleteRow() has a third input parameter now, bNullRow. If this is given as true the row information will be nulled out.
• New: The pagination name is now used (with a prefix of 'paging_') as a class name for the pagination element (.e.g if you are using full_numbers page styling then you could use paging_full_numbers as your CSS selector). This helps to avoid conflicts with multiple paging types, and helps to clear confusion with the example CSS. Examples updated.
• New: Added regular expression filtering demo
• New: fnInitComplete now has a second parameter (useful only for sAjaxSource) - the json return from the server

• Fixed: A blank oLanguage.sUrl will no longer break
• Fixed: Processing language definition now allows HTML to be passed in the string and renders it (brought into line with all other language options).
• Fixed: Incorrect numeric type detection could occur on stings such as yyyy-MM-dd
• Fixed: Typo in printed code (not the actual source) of the server-side processing with pipelining example.

Release comments

Release notes

• New: oSearch and aoSearchCols can be defined in the init object for predefined filtering state
• New: iDisplayStart can be defined in the init object to state where the table should start it's record from

• Changed: Save save - path names are now saved in lower case
• Changed: A title attribute is applied to the paging buttons for the standard pagination (the images are CSS supplied, so no alt attribute)

• Fixed: State saving for individual columns was broken (cookie could get very large). This is now fixed.
• Fixed: Selecting rows works in IE6 now - thanks to Vincent Jones
• Fixed: Demo styles for full_numbers pagination fixed in IE
• Fixed: Complex headers (colspan and rowspan) now work in IE
• Fixed: Server-side processing information display had a few bugs in it - no longer

Release comments

Release notes

• New: Plug-in filtering functions! Allows range filtering and any other custom filtering types you want.
• New: Column filtering state is now also saved when using save state
• New: A select value of -1 for the length (can be done using the sLengthMenu parameter) means "show all"
• New: Example: server_side/post.html - get data using POST rather than GET
• New: Example: api/range_filtering.html - range filtering using a custom filter
• Fixed: Allow aaSorting to be empty
• Fixed: fnDelete() was incorrectly always paging back when used
• Fixed: Nested tables which have a tbody element gave an error - this is now fixed

Release comments

Release notes

• New: General: Support for grouping columns through support for colspan and rowspan on the header
• New: General: aaSortingFixed property for forcing an 'always sort'
• New: Server-side processing: aoColumns.sName - internal name for server-side processing
• New: Server-side processing: sColumns parameter for server-side processing which passes the internal column names and gives the order that DataTables expects to receive data
• New: Server-side processing: Output order can now be defined using sColumns parameter returned from server. DataTables will automatically reorder if not in the expected order.
• New: Example: advanced_init/row_grouping.html
• New: Example: api/row_details.html
• New: Example: server_side/custom_vars.html
• New: Example: server_side/column_ordering.html
• New: Example: advanced_init/complex_header.html

• Updated: Some love for fnOpen() and fnClose(). It's now really quite easy to show a 'details' row in a table (with server-side processing the row will be lost after a redraw).
• Updated: fnOpen class name is now applied to the TD rather than the TR. Provides the same function with a little more flexibility
• Updated: Concatenation of the space to oLang.sPostFix is now done during initialisation
• Updated: The readme.txt file
• Updated: All examples are now in a sensible directory structured
• Updated: Header and footer handling code

• Fixed: fnRowCallback wasn't correctly inserting updated rows
• Fixed: sType is now considered for single column sorting
• Fixed: Information message about maximum number of records when filtering
• Fixed: fnRender() and bUseRendered were a bit mixed up in fnUpdate()

Release comments

Release notes

• New (back ported from 1.5.0 beta 4): Added option for using original data for sorting and filtering (when using fnRender) - bUseRendered
• Fixed (back ported from 1.5.0 beta 4): $ and ^ are escaped as regex characters now
• Fixed (back ported from 1.5.0 beta 4): Filtering with a string as anything but a post fix filtered on the old result, rather than the full table.
• Fixed (back ported from 1.5.0 beta): sClass is now applied to DOM read cells as well as dynamically created ones
• Fixed (back ported from 1.5.0 beta): sAjaxSource didn't do an initial sort on the retrieved data

Release comments

Release notes

• New: Added option for using original data for sorting and filtering (when using fnRender) - bUseRendered
• Fixed: $ and ^ are escaped as regex characters now
• Fixed: Filtering with a string as anything but a post fix filtered on the old result, rather than the full table.
• Fixed: Hidden columns were a little broken
• Fixed: Display overflow check in fnDeleteRow() corrected
• Removed: Language directory in the distribution - language information is now maintained at datatables.net/plug-ins

Release comments

Release notes

• Updated: fnDrawCallback - passes settings object
• Fixed: Set column visibility - fixed for when there is no footer
• Fixed: iDisplayLength was temporarily broken

Release comments

Release notes

• Full support for Adobe AIR - including multi-column sorting (which wasn't in the first beta).
• Slight speed improvement on the normal sort

Release comments

- Support for server-side processing of data
- Ability to get/display data from any source (Gears for example)
- Adobe AIR support
- Ability to show or hide columns programatically through the API.

This is very much a beta release, but it seems to be hold up quite well in my tests, and it also fixes a number of issues that were present in 1.4. I've also build a unit testing framework for DataTables, which will thoroughly test all releases in future, but I'm still in the middle of writing the tests. 1.5 won't be released until I'm happy that I've got a comprehensive test suite (we all want solid software!), but hopefully that won't be too long.

Full details can be found in the forum.

Release notes

• New: Ability to show and hide columns dynamically!
• New: Added example for sorting and type detection plug-ins
• New: Sorting and type detection plug-in
• New: Added a new callback function for pre-drawing - fnPreDrawCallback()
• New: Server side processing - rock on!
• New: fnServerData() init parameter
• New: Support for Adobe AIR (although multi-column sorting is not supported)

• Updated: If the processing display is disabled (which it is by default) then the execution thread involving sorting is now continuous. The old behaviour applies is processing is enabled.
• Updated: try/catch on the eval of the state saving cookie to stop Javascript errors on reading a dodgy cookie

• Fixed: sClass is now applied to DOM read cells as well as dynamically created ones
• Fixed: _fnGatherData() has been optimised
• Fixed: fnOpen() colspan is correct for visible columns now
• Fixed: Column classes weren't correctly applied when using fnSort() API function
• Fixed: Automatic detection of numbers now allows only one decimal place
• Fixed: sAjaxSource didn't do an initial sort on the retrieved data
• Fixed: Removed text align on empty cell and demos now use the class name

Release comments

Release notes

• Fixed: fnInitComplete() is called after the Ajax call has finished if using sAjaxSource
• Fixed: Documentation link in the examples that come with the distribution have been updated with the address of the new web-site
• Fixed: State saving javascript error

Release comments

Release notes

• Updated: Plenty of attention to fnRender() - thanks to mimic on the forum.
• Updated: fnRender()ed data is stored in the internal aoData internal storage array to
• Updated: fnRender callback, aData parameter is now only the row in question - not the entire table

• New: Pass oSettings to fnInitComplete
• New: Add a third element to the array returned by fnGetPosition for TD elements - to indicate the position with hidden nodes
• New: Added a single row get for fnGetNodes()
• New: Use JSON.parse() for cookie if it is available for security. This is recommend.
• New: Regular expression flag for global and individual column filtering is now retained. Therefore you could now enable global regex filtering by doing 'oTable.fnSettings().oPreviousSearch.bEscapeRegex = false;'.

• Fixed: Filtering did not work when using fnRender()
• Fixed: fnUpdate() now considers fnRender()
• Fixed: fnGetData() speed improved for a single row
• Fixed: when initialising an empty table (ajax or aaData) a sorting type of 'string' is not assumed
• Fixed: Bug in _fnColumnIndexToVisible() which could cause issues with fnUpdate()
• Fixed: When oLanguage was specified, the DataTables initialisation process returned too early due to a setTimeout poll. This is only needed for an XHR language file.

Release comments

Along side the release of DataTables 1.4.0, this new web-site has been created to help document DataTables initialisation parameters and API, and also to foster further development of this plug-in. A plug-ins section has been added, and every is encouraged to share their thoughts on the forums.

I hope you enjoy developing with DataTables 1.4.

Release notes

DataTables 1.4.0 is identical to 1.4 beta 11 (except the name...), but here is a quick summary of what is new in the 1.4 series:

• Non-destructive DOM interaction!
• Ajax auto loading of data
• Sorting column(s) highlighting
• Type detection for dynamic data (and plugin support)
• State saving
• API plug-in mechanism
• Speed - v1.4 is considerably faster for most common tasks
• Improved documentation

Release comments

Release notes

• Fixed: State saving in Webkit based browsers
• Fixed: Some state saved information could be over ruled by the defaults

Release comments

Release notes

• New: Turkish language file tr_TR - thanks to Umit Gorkem
• Fixed: oSettings as first parameter to API function rather than the last to allow for variable length argument calls. WARNING - any custom API functions will need to be updated for this change.
• Fixed: Allow HTML inside the full_numbers buttons
• Fixed: State saving in Webkit browsers
• Fixed: Cancel text select for the full buttons numbers when rapid double clicking

Release comments

Release notes

• New: fnUpdate function to update the data currently on display in the table. Takes account of filtering, sorting etc.
• New: fnAddData now has a second parameter, a boolean to indicate redraw required or not (default true)
• Fixed: Nested tables no longer have their rows removed when DataTables redraws!
• Fixed: Remove fnDecrement API function (can be added back as an API function if anyone wants it - but it was broken anyway...)
• Fixed: Remove _fnMasterIndexFromDisplay internal function - unused

Release comments

Release notes

• New: Empty row td now has a class name of 'dataTables_empty'
• New: fnAddData returns an array of integers with the indexes of aoData which have been added
• New: Added Norwegian language file (nb_NO) - with thanks to Petter Ekrann for this translation.
• Fixed: aaSorting can be of zero length
• Fixed: You can pass parameters to custom API functions (with thanks to Benedikt Forchhammer for this fix)
• Fixed: Sorting with individual column filtering (but no global filter) resulted in the column filtering being lost.
• Fixed: Empty row now has asStripClasses[0] applied as a class name
• Fixed: A whole bunch of little improvements to the code thanks to jslint

Release comments

Release notes

• New: Plug-in method for custom API functions
• New: API plug-in example
• New: Package gzipped DataTables as standard (9.2k)
• Fixed: Updated German language file (thanks to Jorg Holz)

Release comments

Release notes

• New: Portuguese Brazilian translation
• New: Added variable length for the 'full_numbers' pagination type thorugh the variable jQuery.fn.dataTableExt.oPagination.iFullNumbersShowPages - with thanks to Jovan Popovic for his work on this!
• Fixed: Save state now works in IE (IE has an issue with the path of a cookie being anything but root)
• Fixed: Save saving with full numbers rejigged slightly
• Fixed: Tidied up a few spaces where there should have been tabs

Release comments

Release notes

• New: Add (optional) third parameter to fnFilter() API function to indicate is regex strings should be escaped or not. Default true.
• New: A couple of extra classes for the 'full_numbers' pagination buttons.

Release comments

Release notes

• Bug fix: Custom defined titles (sTitle) are applied to non-dynamically build tables
• Bug fix: Fix offset issue when using fnRender() with bVisible parameter in the table table

Release comments

Release notes

• New feature: State saving - remember filtering, sorting, pagination and length values after refresh
• New: Russian translation
• Added: Form submit example
• Added: Highlight rows and columns example
• Added: State saving demo
• Remove: Random test file

Release comments

Release notes

• Added: Now ships with jQuery 1.3.1
• Fixed: Single row select example cleaned up
• Fixed: 'information' issue after deleting rows
• Fixed: Regular expression special characters are escaped when used in filtering input
• New: For type 'html' tags are stripped for filtering (no longer match on tags...) - with thanks to Marc-Allen Johnson for his help with this suggestion and code patch.

Release comments

Release notes

• New: Initial release of DataTables 1.4