Commits on Sep 30, 2010
  1. Release: 1.7.3

    committed Sep 30, 2010
  2. Fixed: Now restore the width of the original table on fnDestory. This…

    … is needed for when using sScrollXInner, and on other occasions where using DataTables will force the table to be wider than it otherwise would be - 2840
    committed Sep 30, 2010
  3. Fixed: If a TR height was specified via css globally (for example tr{…

    …height:20px}) this would cause the hidden header and footer in scrolling tables to be shown. Added override by CSS style for this - 2765
    committed Sep 30, 2010
  4. Fixed: Add a sanity check to ensure that the node given to DataTables…

    … is in fact a table - 2343
    committed Sep 30, 2010
  5. Updated: Added link to Marko's post in the forum for the input multi …

    …filter example, giving the code for how to restore the values when state saving is enabled. Thanks Marko - 2864
    committed Sep 30, 2010
  6. Updated: server_side/row_details.html and api/row_details.html both n…

    …ow used live events to make life easier.
    committed Sep 30, 2010
  7. Fixed: Stable sorting algorithm was slightly wrong when dealing with …

    …values which match each other. The idea for the stable sort is that the position shouldn't change so it should do a numeric sort of the row's current positions (the comment reflected this...) but it was in fact doing the sort on the value (aoData index), thus the "stable sort" position would reflect the original starting positions of the data, rather than the current position. The fix is to correctly look up the position of the index in the array and sort on that position (note the array is cloned, so it doesn't try to sort the dynamically sorted positions, which would make the sort unstable) - 2746
    committed Sep 30, 2010
Commits on Sep 20, 2010
  1. Fixed: When initialising multiple tables it was possible (no aoColumn…

    …s given, and different number of columns) for DataTables to get confused and think one table's columns belong to another (due to a non-unique array in the initialisation object which was being wrongly used).
    committed Sep 20, 2010
  2. Updated: Modify the editable example to give the column information a…

    …s well as row to the server.
    committed Sep 20, 2010
Commits on Sep 15, 2010
  1. Fixed: When infinite scrolling, DataTables would clear it's internal …

    …cache of rows on every draw, when server-side processing was being used. This could result in fnGetNodes giving only a subset of the nodes which are visible, rather than the full set (which it now does).
    committed Sep 15, 2010
  2. Starting 1.7.3 development

    committed Sep 15, 2010
Commits on Sep 14, 2010
  1. Fixed: The 'rewind' of the display start point wasn't being calculate…

    …d in the same way for server-side processing and client-side. This was due to a bug in the calculation of fnDisplayEnd for server-side - 2600.
    committed Sep 14, 2010
  2. Fixed: Data casting is now done after fnRender is called. This means …

    …that if you pass fnAddData a number, you'll get a number, and not the number cast as a string - 2611.
    committed Sep 14, 2010
  3. Fixed: jsLint makes the fair point that escape() and unescape() are n…

    …ot standard functions. switched to using en/decodeURIComponent.
    committed Sep 14, 2010
  4. Fixed: Column visibility was not being saved when calling fnSetColumn…

    …Vis. It would require another draw to save the state before - 2635.
    Fixed: Column visibility was not be restored from the state saving cookie. A small tidy up of the column creation code as well - 2635.
    committed Sep 14, 2010
  5. Fixed: When destroying a table which had been filtered to no results,…

    … the 'No results' row was not automatically removed, returning in the table being unable to be re-initialised (since it has a colspan).
    Fixed: Now use escape() and unescape() for state saving cookie with the filtering strings - 2608
    committed Sep 14, 2010
  6. Fixed: When infinte scrolling, the display start count should always …

    …be at 1, rather
    than reflecting the paging that DataTables is using internally.
    committed Sep 14, 2010
Commits on Sep 8, 2010
  1. Fixed: A number of errors jsLint had picked up. Most trivial but wort…

    …h of note are:
    - Fixed incorrect reference for state saving cookie data string which would cause an error in jQuery 1.3 and before
    - Fixed incorrect adding of anti-text selection event listeners being attached to the header elements (to many being added)
    committed Sep 8, 2010
  2. New: It is now possible to have elements created by sDom have an ID a…

    …ssigned to them as well as a class. An extension of the previous class only syntax you can now do something like "#id.class", "#id" or "class" - 2666
    committed Sep 8, 2010
  3. Fixed: Destroying a scrolling table was not correctly reassembling th…

    …e table from it's component parts which are split up for scrolling.
    committed Sep 8, 2010
Commits on Sep 7, 2010
  1. Fixed: fnInitComplete was being called too early for server-side proc…

    …essing. It is now called after the first draw is complete, like the other data sources.
    committed Sep 7, 2010
  2. Fixed: Column widths we being calculated by not applied. Due to the c…

    …olumn width calculation now being done after the header is drawn, the widths need to be likewise done afterwards.
    committed Sep 7, 2010
Commits on Sep 5, 2010
  1. New: Infinite scrolling! Building on the scrolling feature set that w…

    …as introduced with 1.7, you can now have DataTables do infinite scrolling (bScrollInfinite: true), where data is loaded dynamically as and when needed by the user's interaction with scrolling. Infinite scrolling can be used by all DataTables' supported data sources without modification.
    New: The distance from the end of the current scrolling container before new data is added (with infinite scrolling) can be controlled with iScrollLoadGap (which is a numeric value in pixels).
    New: Example (basic_init/scrolling_y_infinite.html) to show how infinite scrolling can be used.
    Fixed: iDraw was not being incremented for a draw that did not use server-side processing.
    committed Sep 5, 2010
Commits on Sep 3, 2010
  1. Fixed: Column width calculations are now done after DataTables has do…

    …ne it's required DOM manipulation. This means that column width calculations are more accurate and take account of dynamic data.
    committed Sep 3, 2010
  2. Fixed: DataTables would unnecessarily add mousedown and selectstart e…

    …vent handlers to TH elements which aren't used for sorting. This is used on sorting columns to prevent text selection when clicking the element to perform sorting.
    committed Sep 3, 2010
  3. New: When using jQuery UI theme option, DataTables will wrap the cont…

    …ents of sortable TH element in a DIV which can then be used to position the sorting arrow accurately across all columns. The required CSS has been added to the CSS files to show this effect.
    committed Sep 3, 2010
Commits on Aug 22, 2010
  1. 1.7.1 version string

    committed Aug 22, 2010
  2. Fixed: Themeroller 1.8 introduced a few changes from 1.7 (main fg-but…

    …ton* > ui-button) which was causing 1.8 themes to not show correctly. This release updates DataTables to use ThemeRoller 1.8 themes by default, but retains 1.7 backwards compatibility for now (to be removed in future) - 1559
    committed Aug 22, 2010
  3. Fixed: fnDestroy didn't restore columns which had been hidden by Data…

    …Tables, resulting in these columns being completely lost - 2569
    committed Aug 22, 2010