Fixes

• State saving and column visibility could cause rendering issues on reinitialisation
• When columns are hidden and ordering, they should still have the header classes applied to indicate ordering.

Examples

• DataTables wasn't being listed in the files loaded in the examples on the site
• Refine the class and id layout example for different frameworks

Docs

• Fix signature for column().search() and columns().search()

Download DataTables 2.1.2

• New: Add support for composer distribution.

Download DateTime 1.5.3

Full details are available below in the release notes, and summary documents are also available:

• New feature notes
• Upgrade notes
• Blog announcement

New

• div feature which can be used to insert text or HTML in the DataTables controlled layout grid. It does not provide any information or control over the table itself.
• layout now has the ability to set class names on the rows and cells of the layout grid. This gives you complete control over the markup that is used to control the grid, allowing it to fully replace all options that exist in dom.
• DataTables styling updated to use flexbox for layout, allowing much more flexibility.
• All styling frameworks updated to have control elements which are in the same position (i.e. an array of items) will now place them side by side.
• All styling frameworks will evenly space layout full row items.
• If no width style or width attribute is found on the table, we now automatically assign the table 100%. If either is found, they are retained. This is done to simplify the HTML needed, and the width attribute is long since obsolete in HTML (although still works). Disabling autoWidth will stop 100% width being assigned automatically.
• Reintroduce the deferLoading option which is used to delay the first request for data when server-side processing is enabled until the second draw of the table.
• Type detection is now far more functional in that it it is possible to specify that at least one data point in a column match a specific test. Previously all data points had to pass a given test (allOf), but now in addition to that an extra function can be given to help limit data selection (oneOf).
• Automatic detection and ordering for accented characters in the data set. This is done by making use of the improved data type detection to allow non-UTF8 columns to continue to use simple ASCII string sorting (for performance), but columns with UTF-8 characters in them will now use localeCompare automatically for sorting, which the locale specified by the end user's browser preferences. Please note that this requires Safari 10.1 or newer if you are using Safari. If you are using an older version, it will automatically fallback to treating the column as a simple string type.
• orderDescReverse option which can be used to disable the reversal of data when doing a descending order. This can make the ordering of data more like how Excel operates when data matches in the column being ordered on.
• language.aria.paginate.number option which can be used to set an ARIA label for the number buttons in the pagination control.
• search.processing option which can be used to show the processing indicator (processing) when the end user types into the search box.
• Ability to control what buttons appear in the paging control through three new options for the feature. This provides similar functionality to paging.type but is more intuitive. It also allows the paging feature code to be more compartmentalised, and will allow a reduction in code size when the deprecated properties are removed. The new options are:
  • paging.numbers
  • paging.previousNext
  • paging.firstLast
• DataTable.use() method which can inform DataTables libraries such as Moment and Luxon in a module loader environment.
• Support for Bulma 1 and Bulma's new dark mode
• Automatically detect d as a string on a JSON response and parse it as JSON for use (if it is valid JSON). This is for improved compatibility with .NET so ajax.dataSrc doesn't need to be specified for this wrapper.
• nav element is now used to wrap around the pagination control. This is done to help improve accessability. To preserve CSS backwards compatibility the host element div.dt-paging is retained, and the new nav is a child of that, with the paging elements and child of that in turn. It means there is an extra tag than can be considered redundant, but that's the trade off for adding the element.

Deprecated

• pagingType and paging.type are now redundant and will be removed in DataTables 3. If you are using these properties it is recommended that you update them when possible.

Updates

• Use button elements for Bootstrap 5's pagination control, as they are more suitable for in page navigation and Bootstrap fully supports this.
• If there are multiple layout items in a single cell, they will now show on the same line on larger screens and collapse to a single column for small screens.
• Disable auto type detection when server-side processing is enabled. Without the full data set available it is unreliable and error prone. If you need specific type actions (e.g. a class name) you can assign a type to a column using columns.type.

Fixes

• Using a <span> in language.lengthMenu could result in duplication of the page length <select> tag.
• aria-sort attribute would not be added to the table if multi-column ordering and the first column to be ordered upon was hidden.
• Don't add tabIndex to the paging buttons if its value is 0 as it is redundant
• Tidy up the order of initialisation when a language file is loaded
• It was possible for date time types to overlap due to the replacement of characters in the name. That is not required as the data type names are just a plain string.
• The new type detection is used to prevent HTML columns without numbers being detected as numeric columns (e.g. this happened with FontAwesome icons in a column).
• Type detection was not running if both ordering and searching were disabled.
• Tighten the date data type detection to make sure at least one cell has a date in it.
• If ajax.url === '' the ajax.data parameter would only correctly trigger once.
• Reordering initial data load to allow data-* attributes to be used to define column data points

Examples

• New examples for grid layout and id/class demonstrations.

Docs

• Add mention of how to restore the DataTables 1.x columns.orderSequence default value to the documentation for that parameter.
• layout update for id and class name options, plus a bit of rearrangement
• Fix link to dt-error
• Reflect that the aria values for pagination are now set in 2.0+

Download DataTables 2.1.0

New

• Option to load custom scripts in print page

Fix

• Tighten up the ISO8601 date detection for Excel formatting. It must be in the date range 1900-9999.

Typescript

• Rewrite how the buttons are defined, so options can be split per button type and other extensions can define their own buttons.
• Add Buttons to DataTables' features

Examples

• Correct styles for multiple styling frameworks

Download Buttons 3.1.0

Fixes

• :visible on its own as a column selector could incorrectly include hidden columns when used with a complex header.
• Selector row indexes from the API could be incorrect when server-side processing is enabled
• Error when checking isShown() for a deleted row

Download DataTables 2.0.8

Fixes

• Scrolling info could be wrong at the end of a fast scrolling action

Download Scroller 2.4.3

Fixes

• Bootstrap 5 table accents weren't shown correctly
• Hidden columns with complex headers were causing a JS error to be thrown

Download FixedColumns 5.0.1

Fixes

• Stop JS error if the order parameter is removed from state saving
• An error would be thrown if columns were hidden inside a colspan group, where the first column in the group was one of those hidden.

Download ColReorder 2.0.3

New

• select.headerCheckbox now has the ability to select only on the current page, or all pages as before.

Fixes:

• When select.toggleable is set, the checkbox should not uncheck on click.
• When range deselecting with a checkbox column, the checkbox clicked on could be unchecked while
  the row was still selected.

Download Select 2.0.3

Fixes

• If inline editing with Editor and escape is pressed, when you blur focus away from a cell it would still submit.

Download KeyTable 2.12.1

Fixes

• Processing element could be cloned if scrolling was enabled
• Scrolling misalignment due to incorrect selector

Download DataTables 2.0.7

Fixes

• Error when the first cell in a header contains a rowspan
• ColReorder would throw an error after a row had been deleted

Download ColReorder 2.0.2

Fix

• A <table> inside the first row of the <tbody> of the DataTable could cause issues when used with scrolling
• Processing indicator, when scrolling is enabled, could be partly hidden under the header / footer elements
• Remove use of negative lookbehind regex, which isn't supported in Safari before 16.4.
• row().node() didn't take account of sparse array in error checking

Performance

• Do not apply sort when there is only one match (#277)
• Major increase in filtering speed

Typescript

• Add support for boundaryNumbers in paging feature
• null was not being accepted as a value for layout

Examples

• Ensure that jQuery is not loaded twice if it is already present on a page

Download DataTables 2.0.6

Fix

• Ability to give a custom class to the row selection checkbox
• Bootstrap 5 integration makes use of this to style the checkboxes

Download Select 2.0.2

Fixes

• Info, when scrolling, was 0 based rather than 1.

Examples

• Correction to Taiwan country name in demo data

Download Scroller 2.4.2