Skip to content
Commits on Feb 1, 2012
  1. DataTables 1.9.0! :-)

    committed
  2. Docs: The options (properties) for the DataTables initialisation obje…

    committed
    …ct that have a default function need an @member tag otherwise they are documented as methods, which they are not.
  3. Fix: Docs: Typo

    committed
  4. Fix: When mDataProp was used to get a nested object, but a parent obj…

    committed
    …ect didn't exist it would throw an unrecoverable error. With this change the behaviour matches that of single level data whereby if data cannot be found, at any level, then undefined is returned from the data get object. This means that if sDefaultContent is defined then that will be used instead, and if not defined an error will still be given (although this one under DataTables' control).
    
    Dev: Removed the "fast lookup" function for data get and set as they weren't really that useful in terms of speed and would require more code to be added to copy with the above change to the error handling for missing objects. Smaller code and virtually no difference in speed. Sold.
Commits on Jan 31, 2012
  1. Docs: Add a "dtopt" tag to options that should be documented on the D…

    committed
    …ataTables main site. This allows that documentation to be automatically generated from the source as well as the auto gen developer documentation.
    
    Docs: Fix a few small issues with some of the documentation comments
  2. Dev: Code size - also in fnSetColumnVis reduce code size with aoData …

    committed
    …references in the same way as we do for aoColumns. Smaller size and more consistency. All good.
  3. Dev: Get the library size back under the target 70000 bytes. Its a bi…

    committed
    …t of a cheap shoot this one, but every little helps!
  4. Docs: API: Underscore function documentation updated to take account …

    committed
    …of allowing TH/TD cells in the selector
  5. New: API: fnGetData now also allows TD/TH nodes to be passed in and D…

    committed
    …ataTables will figure out the data for the cell, returning that - easier than calculating the column index yourself. So you can now get the whole table's data, a row's data or an individual cell's data from the fnGetData function (you could get the cell data before, but you would need to use fnGetPosition).
    
    New: API: Underscore function updated to use fnGetData rather than its internal function calls. Although slightly more expensive in computation terms, it extends the capacibabites of the underscore function greatly, allowing TD nodes to be the result of the selector as well as TR nodes. So now you can get a column of data with something like: $('#example').dataTable()._('td:nth-child(4)') . Cool :-)
    Dev: New internal function called _fnNodeToColumnIndex, adapted from fnGetPosition for reuse.
Commits on Jan 30, 2012
  1. Fix: Remove characters 0x80-0xFF. I had a new non-ASCII characters in…

    committed
    … by mistake and the PHP JSON processor objects to these characters when parsing the output from the JSDoc debug output.
  2. Fix: With scrolling enabled, adding the scrollbar width to the header…

    committed
    … / footer inner container elements could cause the table to resize incorrectly on the following draw (and this error was cumulative). Fix is not to adjust the inner element for the scrollbar width - makes no difference to the table draw. It is possible that if you've styled this element you might need to take this change into account, but by default DataTables will style the parent (scrollHead) so no change is required (regardless of jQuery UI theming enablement) - 6776.
    
    Fix: The calculation to detect if the scroll bar would be shown in IE6/7 was incorrect - it was calculating the height of the entire table, rather than just the body of the table (i.e. body + header + footer) which caused the "correct" for the scrollbar to be incorrectly applied to small tables.
Commits on Jan 28, 2012
  1. Examples: Fix: SyntaxHighlighter was having problems with copy and pa…

    committed
    …ste in webkit browsers - fix pushed to syntax highlighter here: https://github.com/alexgorbatchev/SyntaxHighlighter/pull/86 - this is the commit of that fix to the local copy
  2. Dev: Trivial modification to bring 1.9.0 back under the target size o…

    committed
    …f 70000 btyes (was only 4 out). Simply reference the previous search object to a local variable so the compressor can compress more
Commits on Jan 25, 2012
  1. DataTables 1.9.0.dev.4

    committed
    Fix: Multiple tables were going haywire on initialisation due to the self reference - 8233
  2. DataTables 1.9 beta 3

    committed
  3. Fix: aoPreSearchCols can be given as null if you want to deinfe multi…

    committed
    …ple columns - doing so would have resulted in an error. Fixed (unit test)
Commits on Jan 23, 2012
  1. Dev fix: Documentation - noted that there were three parameters passe…

    committed
    …d to mDataProp as a function, but only documented two. Add documentation for the third...
Commits on Jan 22, 2012
  1. Update: mDataProp update to make it more versitile as a function and …

    committed
    …fix the settings of data with mDataProp. When mDataProp is given as a function, the function is now called with a 'type' of 'set', which the developer using mDataProp must used to store the value that if given (otherwise DOM read values would not be stored!).
    
    Update: mDataProp documentation - example of using mDataProp as a function and clearer information about the options for mDataProp
Commits on Jan 21, 2012
  1. New: API method: _ - the underscore function is the compliment to the…

    committed
    … $ function introduced early in the 1.9 development cycle. While working with DataTables and the $ I've often wanted the data for the nodes that I'm working with, which means a call to fnGetData and an inner look - not itself bad, but it means an area loop in the external code - so this underscore function is basically the same as $, but rathe rhtan returning an jQuery object of nodes it will return an array of the data source objects for the matched TR elements (important to note that - the selector should resolve TR elements only, other elements don't have DataTables controlled data, and thus will be null in the returned array)
  2. Removed: Column reordering example using sName - it is much better to…

    committed
    … use mDataProp for this kind of thing now and column reordering is depricated in the 1.9 release of DataTables, so remove the example showing how it might be done to stop new users using it.
Commits on Jan 20, 2012
  1. Dev: Update: _fnNodeToDataIndex can be made _so_ much faster with the…

    committed
    … new _DT_RowIndex prviate parameter - so this commit does so :-)
  2. Dev: New: _DT_RowIndex is a private parameter that is attached to all…

    committed
    … TR elements in the table now. This allows fast reverse mapping from the row index to the aoData entry (typically this will be used for getting _aData). Before we would have to loop over all rows which could be very slow, but this reverse mapping allows several new options for optimisations and future enhancements.
    
    Dev: Updated: All fnRender calls have been put into a single point - code reuse...
  3. Dev fix: The last change for fnAddData was incorrect - it would mean …

    committed
    …that objects couldn't be added...
Commits on Jan 19, 2012
  1. DataTables 1.9.0.dev.3

    committed
    Fix: fnAddData - check for 2D array could fail on null, since null is an object type - 8134
Commits on Jan 15, 2012
  1. Reissuing 1.9.0.beta.2 - the one I tagged before was never released o…

    committed
    …utside me tagging it, since there was no time to write up the release notes, and now with a few more bug fixes, I think they should be rolled into to what will be released as 1.9.0.beta.2
  2. Fix: When a previous search column details is defined for column 0, i…

    committed
    …t would fail incorrectly. Now fixed
  3. Fix: Backwards compatibly for fnGetData and fnGetNodes when the row (…

    committed
    …as an integer) is not available
  4. Fix: fnOpen - when passed a TR element (or indeed any other element) …

    committed
    …that is not part of the master table (i.e. under control of DataTables), DatTables would try to "open" the row anyway - which was wrong. So now check that the node given is a TR element under control of DataTables, otherwise silently return. This is useful for using fnOpen when bound to all TR elements in the TBODY with a live event handler (i.e the click would also occur on the opened row).
Commits on Jan 14, 2012
Something went wrong with that request. Please try again.