Commits on Mar 2, 2011
  1. Fix: When removing stripe classes, look only at the direct tbody tag,…

    DataTables committed Mar 2, 2011
    … not nested which could remove classes you want to keep!
Commits on Mar 1, 2011
  1. Fix: Modify unit tests for all warnings enabled in PHP and remove dep…

    DataTables committed Mar 1, 2011
    …ricated function calls
  2. Fix: With all warnings enabled in PHP, there were certain DataTables …

    DataTables committed Mar 1, 2011
    …initialisations which could trigger warnings in the example server porecessing script.
Commits on Feb 27, 2011
  1. Fix: Internal footer height for scrolling table should be set to 0, j…

    DataTables committed Feb 27, 2011
    …ust like the header is
Commits on Feb 26, 2011
  1. Fix: When unbinding DT namespaced events in fnDestroy, also unbind an…

    DataTables committed Feb 26, 2011
    …ything attached to the wrapper element
  2. Fix: Namespace all events added via jQuery (using the 'DT' namespace)…

    DataTables committed Feb 26, 2011
    … to make events easy to remove in fnDestroy.
    Fix: Remove all added events in fnDestroy, otherwise DataTables will leak memory like crazy when the destroy function is called
Commits on Feb 24, 2011
  1. Fixed: The scrolling header container should really be width:100% rat…

    DataTables committed Feb 24, 2011
    …her than a fixed width. The pixel width was trying to do width:100% and succeeding, but needing to be calculated rather than done natively.
Commits on Feb 22, 2011
  1. Fix: fnUpdate wasn't updating cells which were hidden by fnSetColumnV…

    DataTables committed Feb 22, 2011
    …is or bVisible. It does now.
Commits on Feb 17, 2011
  1. Fixed: fnGetData and fnGetNodes to return null when a row number is p…

    brewski committed with DataTables Feb 17, 2011
    …assed in that is out of the table's range.
    Signed-off-by: Allan Jardine <>
Commits on Jan 29, 2011
  1. Fixed: The instance that is stored (oSettings.oInstance) could contai…

    DataTables committed Jan 29, 2011
    …n muliple tables in a single instance, when tables are created with a selector that includes multiple tables. This could make API access a bit more tricky (3963) so now store a unique instance of the DataTables object for each individual instance.
Commits on Jan 27, 2011
Commits on Jan 25, 2011
Commits on Jan 18, 2011
Commits on Jan 17, 2011
  1. Bump version to

    DataTables committed Jan 17, 2011
  2. Fixed: Table width calculations need to be done on the outerWidth, ra…

    DataTables committed Jan 17, 2011
    …ther than 'inner', otherwise things simply don't add up (and IE get's a bit confused - fair enough).
Commits on Dec 15, 2010
  1. Finish 1.7.5 development

    DataTables committed Dec 15, 2010
  2. Fixed: fnInitComplete was not the last thing to be executed when usin…

    DataTables committed Dec 15, 2010
    …g DOM source. IT was possible that you could set sAjaxSource in fnInitComplete which would then trigger DataTables to do an Ajax call incorrectly.
Commits on Dec 14, 2010
  1. Fixed: fnDrawCallback was actually the first of the draw callback fun…

    DataTables committed Dec 14, 2010
    …ctions 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.
Commits on Nov 28, 2010
  1. Performance: Re-written the sorting implementation so it doesn't use …

    DataTables committed Nov 28, 2010
    …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
Commits on Nov 18, 2010
  1. Updated: fnAdjustColumnSizing when called with 'false' as the first (…

    DataTables committed Nov 18, 2010
    …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.
  2. Updated: fnAdjustColumnSizing when called with 'false' as the first (…

    DataTables committed Nov 18, 2010
    …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.
Commits on Nov 17, 2010
  1. Fixed: The behaviour for complex headers has been altered slightly fo…

    DataTables committed Nov 17, 2010
    …r 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.
  2. Updated - now using jQuery 1.4.4 as the copy of jQuery included in th…

    DataTables committed Nov 17, 2010
    …e DataTables distribution. Passes all unit tests
  3. Fixed: When using server-side processing and having called fnDestroy,…

    DataTables committed Nov 17, 2010
    … don't make another XHR to the server as the data won't be used - 3375
Commits on Nov 4, 2010
  1. New: Add bScrollAutoCss option (default true). This allows you to con…

    DataTables committed Nov 4, 2010
    …trol 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).
Commits on Nov 2, 2010
  1. New: Column visibility options in DataTables (bVisible and fnSetColum…

    DataTables committed Nov 2, 2010
    …nVis) 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.
Commits on Oct 31, 2010
  1. Fixed: Remove the 'sNames' parameter that was introduced for server-s…

    DataTables committed Oct 31, 2010
    …ide 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