Fix: Column width calculation could be incorrect when not using any user defined widths or hidden columns.Rather than a new API instance being explicitly created for every item, use the existing instance as the basis for the selector.
Fix: Performance improvement for the every() methods.Fix: Some reset stylesheets will set vertical-align:baseline on all elements, which causes the header cells in a table body to be visible.Fix: Chrome has an odd bug whereby the max-height needs a reflow in order to be correctly calculated - otherwise a gap could appear at the bottom of the table.Fix: If scrollX is enabled for a table that doesn't need horizontal scrolling, but does have vertical scrolling, when the table is filtered to have no vertical scrolling the columns would be misaligned due to the column widths not being recalculated for the new table width.Fix: in cells could cause column alignment errors as it was being counted as 6 characters rather than 1 in the find longest string method.Now the column width calculation will remove this sub-pixel issue by rounding up and also keep a track of the table width itself rather than reading from the DOM.
Basically this came down to the width of the table not equalling the width of the cells in the table and if the column widths assigned and the table width assigned did not match perfectly, IE would ignore the column widths assigning and layout as it saw best.
Update - docs: Note the focused selector modifier option from KeyTable 2.1.Update: Add column index information to the Requested unknown parameter error message to provide additional debug info.Update: A scrollX table is now allowed to collapse horizontally - simply don't specify style="width: 100%" or width="100%" for your table in the HTML and it will be allowed to collapse if the columns are smaller than the space required.Update: Allow a window to be passed in for CommonJS factory which gives DataTables the ability to be used in a headless environment (server-side rendering for example).Update: $.fn. will now return the original value rather than NaN if the value cannot be parsed as a number.New: order.fixed() to get / set the fixed ordering of the table.New: Pass the recalculation parameter through to the column-visibility event allowing listeners to optimise for it.Particularly useful if you wish to use icons in place of the button text. New: options which can be used to specify ARIA label attributes for the pagination buttons.
It will basically encode HTML entities so they are shown in the rendered view rather than being written directly as HTML. New: $.fn. renderer method that can be used to help prevent against possible XSS attacks.New: CommonJS will load jQuery if it wasn't passed in.New: DataTables no longer defines itself as a named AMD module.A blog post will follow shortly detailing how these packages can be used. DataTables and styling packages to integrate it with Bootstrap, Foundation, jQuery UI and of course its own styling, are now available on NPM and Bower under the name. Of particular note is the reworking on the CommonJS and AMD loaders that DataTables and all of its extensions use to use a consistent naming structure. This release is an important update for DataTables 1.10 addressing a number of issues that can been found since 1.10.9, improving its module loading capabilities accessibility and security.
This software was originally released on 8th November, 2015. DataTables CDN files for DataTables 1.10.10.