Allan Jardine
6b605936f7
Update: Significant update to how sorting is applied internally in DataTables - there is no difference to how the sort is actually done, with the single exception that the -asc and -desc are not depricated in favour of the -pre method only.
...
- With the introduction of the -pre method in DataTables 1.9, the -asc and -desc sorting functions became more or less redundant since they are simple comparisons (all of the complexity is now in the -pre formatting function). As such the call to the -asc / -desc method is overhead that really isn't needed, and this commit introduces a sort function that doesn't call the -asc / -desc methods, instead just doing the comparison itself. In tests, this relatively simple change leads to a performance improvement of around 15% in all browsers (it also has the side benefit of less operations, so IE8- will be able to sort larger tables before flagging up a slow script warning).
- We can't just remove the sorting method which will call -asc / -desc though since not all sorting plug-ins will have a -pre method. Therefore, for backwards compatiblity the old sort function (albeit updated for the changed variables) is retained. The backwards compatibality code adds around 300 bytes to the library, but this is an unaccounced change, so backwards compatiblity must be retained.
- The old sort method will be removed in v1.11. The -asc and -desc methods are now fully depricated.
- Altered the sorting method to flatten the aaSorting array since the introduction of aDataSort in v1.9 required an extra loop in several locations. The functionality is very useful, but the extra loop can be a bit messy and slightly hit performance, so it is now flattened to be a single array (with object information so it makes sense, rather htan array indexes!).
- Altered the order of sorting when building _aSortData since it was looking up the same variable smultiple times which really wasn't needed.
This is part of a small incremental changes plan for DataTables! There are still a huge number of things to improve in this area, but this is a nice clean up and a nice 15% sorting performance improvement to get us started :-).
2012-09-29 21:25:41 +01:00
Allan Jardine
36076fc5c8
Removed: sName reordering on return from the server when server-side processing. This was depricated in DataTables 1.9 and is now removed. This was an inefficient way to supply data to the DataTable in an array that was out of order and the client-side would reorder the arrays into what was needed. The way to do this now is to use mData and JSON objects rather than arrays, as it provides much greater flexibility without a performance hit on the client-side.
...
Note: _fnColumnOrdering is left in place at the moment, although it may be updated as work progresses on 1.10 with regard to the increased use of column names.
2012-09-23 18:49:11 +01:00
Allan Jardine
8d56d0204e
Starting DataTables 1.10 development :-)
...
Removed: fnRender - fnRender was depricated in 1.9 and is now being completely removed here. Its always been a bit messy and is now superseded by mRender. The main reason for this is that DataTables use to take an independent copy of the input data source object / array. This is a performance hit and it means we can't do any binding to external objects (for example it makes Knockout integration almost impossible).
Removed: bUseRendered - with fnRender being removed, bUseRendered is irrelevent
Updated: With fnRender being removed we no longer need to take an independent copy of the data source object / array (since DataTables itself isn't ever going to write to it now - fnRender did and the copy was included so we didn't inadvertantly change a developers data source object without them knowing about it. This is no longer a problem, and in fact having it use the same data source object is extremely useful in many cases.
2012-09-23 18:38:25 +01:00
Allan Jardine
822c62d05d
DataTables 1.9.4
2012-09-23 14:16:14 +01:00
Allan Jardine
26d2926390
Fix: Ie9 throws an error when document.activeElement is used inside a frame or iframe... So need to wrap the test up in a try/catch. Nasty.
2012-09-23 13:12:39 +01:00
Allan Jardine
b4cd9f11c6
Fix: A header made of only TD elements wasn't being correctly detected - 11705
2012-09-19 07:27:11 +01:00
Allan Jardine
d1142e1450
Fix: If the user is currently focused on the filtering input element, don't overwrite the value that is already shown as this will effect the cursor position.
2012-09-16 12:00:36 +01:00
Allan Jardine
a19e1dee12
Dev: Use className for the newly created TR - slightly faster than addClass which isn't needed here
2012-09-16 11:19:53 +01:00
Allan Jardine
e25b377ee8
Fix: State saving deletion of cookies was somewhat broken. It would delete cookies out of order, which is not what we want. Rewrite how the 'overage' of cookies (4K limit) is handled
2012-09-13 18:13:32 +01:00
Allan Jardine
a43714bfba
Fix - docs: sNext and sPrevious referened to full_numbers pagination type, but they can be used for any pagination control: 9192
2012-09-12 07:47:29 +01:00
Allan Jardine
66e92ab655
Fix - docs: Documentation error for fnGetPosition - missing one of the return indexes - 11708
2012-09-11 10:09:03 +01:00
Allan Jardine
ca96ed55d5
Fix: Remove irrelevent and broken bSortable check for the column options - fix issue #101
2012-09-11 07:04:41 +01:00
Allan Jardine
0a3793b4bb
Dev: Tidy up the way that the header and footer elements are 'got'. Based on pull request #92 .
2012-09-09 18:43:57 +01:00
Allan Jardine
df614240cf
Update: Fully deprecate fnRender - it will be removed from the next major version of DataTables and it is strongly adviced that you do not use it!
2012-09-09 12:26:57 +01:00
Allan Jardine
880de42c6e
Dev: Remove debug from last commit...
2012-09-09 12:05:20 +01:00
Allan Jardine
555aacfc6d
Fix: mRender and mData now work in the same way for DOM sourced tables as they do for JS sourced table data. Generally we wouldn't really expect them to be used as much for DOM sourced tables (if you want your table formatted differently, you'd just create the HTML differently!), but it can sometimes be useful to use these options. This also brings mRender to full 'pace' ready to be used in complete preference to fnRender (alongside the other methods for cell rendeirng such an fnCellCreated etc).
2012-09-09 11:57:02 +01:00
Allan Jardine
59dc2aed9c
Dev: Fix a couple of issues that were introduced in pull request #85 - 1. Mix of spaces and tabs :-). 2. documentation generation was broken due to the use of another closure, 3. minification was broken as window, document, undefined were been aliased and 4. jshint was throwing errors. This addresses those issues, primarily by shifting the closures around.
2012-09-02 10:33:49 +01:00
Allan Jardine
e69e3c6c1c
Dev update: Commit built changes from Tim Tucker from last few merges
2012-09-02 09:49:17 +01:00
Allan Jardine
0d47107906
Merge pull request #84 from timtucker/master
...
Update to docs
2012-08-31 09:46:34 -07:00
Tim Tucker
08619a3a21
Update media/js/jquery.dataTables.js
...
Update doc to reflect that _fnGetWidestNode returns a node, not a string.
2012-08-31 10:48:55 -03:00
Allan Jardine
c2af41140b
Performance: Large improvement in scrolling performance due to rearranging the way that column widths are read and applied to the target table. Rather than merging reading and writing together, we now seperate the reading and writing phases, allowing the browser's rendering engine to optimise the reflow. Props to jlabanca for this modification - 11541
2012-08-30 07:29:50 +01:00
Allan Jardine
9f8d2a632b
Moving on to 1.9.4 development
2012-08-22 16:41:52 +01:00
Allan Jardine
34096537c2
Fix: Firefox Windows (not Mac) had an error when calculating if scrolling oversizing was needed or not (_fnBrowserDetect). The result was that the table did not fill the space when y-scrolling was enabled and Firefox Windows was used. Fix is to remove the height on the DT_BrowserTest parent as suggested by randomuser - 11406
2012-08-22 16:39:36 +01:00
Allan Jardine
b16efbc62a
DataTables 1.9.3 :-)
2012-08-08 22:39:39 +01:00
Allan Jardine
725c1b68ba
Fix: Typos in documentation comments and source comments - 11083
2012-08-08 22:22:45 +01:00
Allan Jardine
1f0b162760
Dev fix: In the update to the search array building methods I neglegted to strip \n\r from all rows (only HMTL rows were being stripped) - this is required for searching to work as expected. Picked up by the unit tests.
2012-08-08 22:05:14 +01:00
Allan Jardine
fd0e0a42e4
Fix #39 - null values should also be considered like undefined values when working with nested data and have properties created as needed.
2012-08-08 20:16:40 +01:00
Allan Jardine
9a7613362f
New: xhr event now has the json returned from the server as the third parameter.
2012-08-08 16:29:27 +01:00
Allan Jardine
9c51aa0ad7
New: xhr event
2012-08-08 16:27:42 +01:00
Allan Jardine
320f53e217
New: When making an Ajax call for data (fnServerData) and the server responds with the JSON parameter "sError" set, Data
...
Tables will alert this out. Typically end users should never see this - it is useful for error reporting from the server
though.
2012-08-06 20:41:49 +01:00
Allan Jardine
ed935f3fb8
New: When making an Ajax call for data (fnServerData) and the server responds with the JSON parameter "sError" set, DataTables will alert this out. Typically end users should never see this - it is useful for error reporting from the server though.
2012-08-06 20:39:57 +01:00
Allan Jardine
45a6d2b505
Fix: null values that were applied to extended object properties were not being correctly applied since typeof null === 'object' - 11180
2012-08-04 09:34:26 +01:00
Allan Jardine
5311067cd2
Dev: Tidy up _fnColumnIndexToVisible and _fnVisibleToColumnIndex to use the new _fnGetColumns method.
2012-07-31 09:39:51 +01:00
Allan Jardine
d034d187bd
Performance: Alter how _fnBuildSearchRow works to be much faster. For this a new method call _fnGetColumns is introduced which will pluck the column indexes that we want into an array that can then be iterated over (rather than spinning over the full aoColumns array twice, we now do it only the once for columns which are actually marked as searchable). Also use array join rather than string concatination to keep the number of operations down as much as possible. The callers of _fnBuildSearchRow must now pass in the data to be searched, limited by the searchable flag (i.e. call _fnGetRowData with the column indexes from _fnGetColumns).
...
Fix: Use jQuery html() and text() for HTML data to search method. Much tidier and copes with strict XHTML - downside is that it is a little slower if & is in a data string.
2012-07-31 09:25:35 +01:00
Allan Jardine
a3a4619f12
Fix - documentation: Two syntax errors in the examples, one for fnStateSaveParams and the other mDataProp - 11083
2012-07-30 10:04:42 +01:00
Allan Jardine
d155f7a7e7
Updated: Renaming mDataProp to mData for naming consistency and to show its flexibility. Please note that this is a backwards compatible change! DataTables will automatically check for mDataProp on a column and use that if required (if both mData and mDataProp are given then the new mData is used in preference).
2012-06-29 20:08:52 +01:00
Allan Jardine
4886322183
New: mRender option for columns - this is effectively a simpiler version of mDataProp for reading data only (while mDataProp also sets data), and much more comprhensive than fnRender (as such fnRender is now offically deprecated). See the documentation comments in model.defaults.columns.js for further information on how to use mRender.
2012-06-29 19:37:22 +01:00
Allan Jardine
0ed6ceda95
Updated: mDataProp syntax now has the ability to accept array syntax (for example "access[].name" would get an array of the 'name' properties from the access property of the data source). This is exceptionally useful for manipulating arrays - however, you are very _strongly_ advised not to use in in mDataProp itself, since when setting arrays, you will overwrite the old array (thus destroying any other properties that it already has!). Instead, see the new mRender property if you want to make use of this syntax for drawing the table.
2012-06-29 17:47:00 +01:00
Allan Jardine
56b0d11c96
Fix: When fnUpdate is called with a column index given, assume that the update is for an individual cell (which the API call has specified, so this is the correct thing to do). This also lets us tidy up some of the code in fnUpate, partiuclarly when regarding deeply nested options.
2012-06-26 17:09:03 +01:00
Allan Jardine
a022e2f736
Dev - remove debug
2012-06-25 20:06:19 +01:00
Allan Jardine
40a236a7cc
Update: Remove use of $.browser since this is depricated in jQuery 1.8 and will be completely removed in jQuery 1.9. Instead we now use feature detection to determine if there is a browser bug with the width calculation of scrolling elements that needs to be worked around. This does unfortunatly increase the code size a bit - it is either this or using user agent string detection (which is exactly what is being removed from jQuery).
...
Starting 1.9.3 development
2012-06-25 11:19:56 +01:00
Allan Jardine
1bd6b29fe4
DataTables 1.9.2 :-)
2012-06-22 08:19:26 +01:00
Allan Jardine
1055d27887
Fix: Regex filter escaping wasn't escaping the dash ('-') character believe it or not. That's been there since very early DataTables!
2012-06-13 18:27:04 +01:00
Allan Jardine
284658e3c9
Fix: When setting deeply nested object properties, where the parent object doesn't yet exist, don't just silently fail. Since we are setting a value, we are at liberty to create the parent object and then set the value - this now does so.
2012-06-07 09:43:47 +01:00
Allan Jardine
29e0d112cb
Fix - docs: Add jqXHR saving to fnServerData example
2012-06-01 07:42:01 +01:00
Allan Jardine
3d802a685b
Fix - docs: JSDoc syntax errors which were picked up by JSDoc Toolkit
2012-05-20 10:55:23 +01:00
Allan Jardine
391cd6a7a6
Fix - API: $ method, when used with defered rendering, when all rows have not been rendered, results in jQUery trying to perform a selector on 'null' which throws an error. Now check for the tr having being created before adding it to the array to pass to jQuery - 8862
2012-05-20 10:33:35 +01:00
Allan Jardine
b64dda47c3
Fix: fnDeleteRow could cause the page to drop back by one - 9505
2012-05-02 07:05:00 +01:00
Allan Jardine
49fe9f2e0e
Fix: Calling fnClose in fnPreDrawCallback would result in an error - 9702
2012-04-29 18:57:37 +01:00
Allan Jardine
d512e8cce7
Dev - build the last change ( fee3ba7)
2012-04-29 10:15:51 +01:00
Allan Jardine
c2a2b4f531
Fix - docs: fnStateLoad example has a spare parameter (although not in the parameters list). Removed
2012-04-29 08:23:17 +01:00
Allan Jardine
2884ee23d2
Start 1.9.2 development
...
Fix - docs: sDom default had an error in it for the closing bracket
2012-04-27 16:17:22 +01:00
Allan Jardine
ba85dc22d6
DataTables - 1.9.1 release :-)
2012-04-15 19:16:24 +01:00
Allan Jardine
9ec52faec5
Dev fix: The change to set all Ajax properties has a knock on effect on setting deep objects that don't exist, since that is now attempted. Picked up by unit test.
2012-04-13 17:56:46 +01:00
Allan Jardine
814ce1f7d5
Update: Bring the mDataProp as a function functionality to parity for Ajax / JS sourced data and DOM sourced data. Previously DOM sourced data would call the 'set' option for the mDataProp function but Ajax/JS sourced data would not, resulting in the set option never being called for those table types, which is a total bummer when you want to do some formatting in the set option. So now it is called. I was slightly conerned about the performance hit since this means a couple of extra function calls for each cell, but its all in JS, no DOM and I can see virtally no difference with about 50'000 rows and 5 columns of data, so acceptable for the benefits.
2012-04-13 17:25:25 +01:00
Allan Jardine
513d6d5440
New: "destroy" event - when the table is destroyed the destroy event is now triggered. This is very similar to how aoDestroyCallback worked before, but this brings the implementation into line with the newer callback/events mechanisim used in DataTable
2012-04-13 15:26:30 +01:00
Allan Jardine
ac9e454e11
New: Column option "sCellType" - allows you to create TD (default) or TH cells for a column. Useful for creating row headings in the TBODY.
2012-04-13 13:31:02 +01:00
Allan Jardine
732d25b229
Fix: IE8 bug where an empty string read from a DOM input element is JSON encoded as '"null"' - absolutely mental! See this blog post for more information http://blogs.msdn.com/b/jscript/archive/2009/06/23/serializing-the-value-of-empty-dom-elements-using-native-json-in-ie8.aspx .
2012-04-13 11:56:01 +01:00
Allan Jardine
773c88b9f6
Fix: When mDataProp is given as a function, an error in getting the data would be rather ugly - 8400
2012-04-13 11:40:45 +01:00
Allan Jardine
8a66adc2d4
New: The _START_, _END_, _MAX_ and _TOTAL_ macros for the information language strings can now be used in any info string, rather than being limited to just the ones noted in the documentation - a new internal function called _fnInfoMacros is introduced to allow this to work - 9211
2012-04-13 11:29:56 +01:00
Allan Jardine
2a60a96177
New: Static API method - fnVersionCheck same as the version check that is already available as an instance method, but here available as a static API method attached to $.fn.dataTable
...
New: Static API method - fnIsDataTable - check if a TABLE node is a DataTable or not
New: Static API method - fnTables - get the DataTables that are initialised on the table (optionally limit to just the visible tables)
Examples update - Tabs and scrolling updated to use the new static fnTables method
Fix: Settings object model was missing the nScrollHead and nScrollFoot properties from the documentation
2012-04-13 10:44:25 +01:00
Allan Jardine
0518525f59
Fix: Captions which were positioned using caption-side:bottom (CSS) would be positioned incorrectly if using a scrolling table. Need to work around webkit bug 83867 to address this and add an empty tfoot element if one is not given - 2022
2012-04-13 09:25:47 +01:00
Allan Jardine
4be9b362c8
Fix: When scrolling and row height collapse was enabled, it was possible that the table column width applied would be too small due to the fact that a scrollbar would be shown for a fraction of a second, due to the height of the scroll body container enforced by the scroll collapse. Fix is to take into account the header height before the width calculation is done
2012-04-12 17:27:05 +01:00
Allan Jardine
3a27a605b9
Fix: Scrollbody height in IE7- - use offsetHeight consistently - 9424
2012-04-12 09:25:35 +01:00
Allan Jardine
5114e98a93
API - fix: The parameter for fnDraw was inverted by mistake in the 1.9.0 release - 7825
2012-04-04 08:28:35 +01:00
Allan Jardine
35a23adb75
Dev fix: Missed a variable def in the recent _fnLanguageCompat change
2012-04-02 11:53:13 +01:00
Allan Jardine
cd0babca54
Fix: IE6/7 return an empty string for getAttribute('id') when there is no ID attribute, rather than null. As such tables were not automatically being given an ID when they didn't have one, which created a situation where the settings object for a table could be 'lost' in IE6/7. Now check for empty string when checking the table ID.
2012-04-02 10:25:52 +01:00
Allan Jardine
04d4786455
Fix: IE6/7 when scrolling is enabled could loose the sorting event due to the way cloned nodes work in those browsers. Note that this was introduced after 1.9.0. Related - jQuery bug 10437 - http://bugs.jquery.com/ticket/10437
2012-04-02 10:03:47 +01:00
Allan Jardine
c1e40a8596
Fix: Language backwards compatibility could override developer defined defaults - 9267
2012-03-30 15:30:19 +01:00
Allan Jardine
e815062197
Fix: When -1 is selected for the display length (show all) the full numbers paging control didn't show page '1' - 9170
2012-03-30 07:48:33 +01:00
Allan Jardine
dec097ef50
Docs - fix: Show oSettings parameter in fnDrawCallback example - 9067
2012-03-26 07:50:38 +01:00
Allan Jardine
1d62b40f66
Docs - fix: Typos
2012-03-21 08:53:21 +00:00
Allan Jardine
f883df1afd
Docs - fix: fnSort documentation updated to indicate column sorting - 9094
2012-03-21 06:49:24 +00:00
Allan Jardine
2096244c60
Fix: afnSortData functions were not being executed with the DataTables instance's scope
2012-03-19 12:09:49 +00:00
Allan Jardine
b5f4938d7d
Fix: If sType for a column is html and the data is null, then _fnDataToSearch could throw an error - 8987
2012-03-14 07:51:07 +00:00
Allan Jardine
c22dfe00d3
Strip HTML from the aria-label tag for the sorting headers
2012-03-14 07:04:33 +00:00
Allan Jardine
918a065f21
Add documentation note on the fact that mDataProp as a function can get a 'type' of undefined when raw data is expected to be returned
2012-03-10 11:34:38 +00:00
Allan Jardine
cc42c49ec3
New - initisalisation: iDeferLoading can now also be an array allowing the developer to specify the number of records before and after filtering for the information display - 7936
2012-03-03 07:34:11 +00:00
Allan Jardine
fc730e17f3
Fix: The fnServerData error function can use the internal logging function now adays - make it do so - 8763
2012-02-29 10:33:03 +00:00
Allan Jardine
3a40c3a440
Fix: The sStripeOdd / sStripeEven options for the class objects were not being applied to the table. The fix is to set the default for asStripeClasses to be null, and then if null is found there, then the user hasn't applied a default, nor have they overridden the default, therefore we can use the classes from the class objects - 8770.
2012-02-29 09:09:16 +00:00
Allan Jardine
e40d1edebc
Fix - docs: Link to sDom from bFilter was incorrect
2012-02-28 10:35:46 +00:00
Allan Jardine
5479600611
Fix - performance: Don't extend the passed in data a second time - its a waste of time
2012-02-26 19:12:11 +00:00
Allan Jardine
126a4fe44e
Fix: When scrolling is enabled the initial width of the header was being set to 150% which was a bit random and could result in the header flashing its display in the wrong place when loading. The fix is to use 100% unless x-scrolling is being forced, at which point it needs to match the inner table - 8332
2012-02-25 07:56:27 +00:00
Allan Jardine
872dc0db3e
Fix: Feature match the server-side sorting to the client-side sorting for what information is sent to the server for sorting. Previously aDataSort was no honored - https://twitter.com/#!/naomiaro/status/172397914239414272
2012-02-22 19:47:09 +00:00
Allan Jardine
bc756f3a69
Docs fix: fnStateLoad documention refered to fnStateSave instead of itself
2012-02-21 14:14:13 +00:00
Allan Jardine
793020a8d4
Updated: When throwing an error, throw a "new Error()" so we can get a bit more information about the error
...
Updated: When using custom sort data types, if the returned array is not of the required length (aoData.length), then an error is thrown
2012-02-20 08:15:28 +00:00
Allan Jardine
409edd791b
Fix: When sorting non-string data as a string (type to type detection) then DataTables 1.9 would automatically convert the non-string data to an empty string so it can be sorted. This can result in unexpected ordering in the table. The fix is to check for a toString() function that is available for the data and if it is there, then use it (great for numeric data, dates etc), otherwise the empty string is used (null, methods without toString). This brings 1.9 back into line with how 1.8 behaved - 8549
2012-02-17 09:29:41 +00:00
Allan Jardine
af2e153bc3
Fix: When updating the filtering input control, we would just match on INPUT elements, so if the developer had appended an input button to the filter wrapper, that value would also be changed - 8537. Now a reference to the input element is stored and used to update the input value (this method means we don't need to add another class option, and developers can change to 'type=search' if they wish).
2012-02-15 09:36:51 +00:00
Allan Jardine
431b5e8a55
Fix: IE8 doesn't like the console check in logging - make it object based on window - 8517
2012-02-14 08:44:34 +00:00
Allan Jardine
ca009fdf88
Fix: When scrolling the column matching would remove any nested THEAD and TFOOT elements in the table - 8423
2012-02-08 08:34:39 +00:00
Allan Jardine
6021360da1
Docs: Fix - Parameter for filtering options in state saving examples should be oSearch, not oFilter - 8408
2012-02-07 14:28:46 +00:00
Allan Jardine
68975aff10
Docs: Fix - fnStateSaveParams refered to fnStateLoadParams in the example code - 8408
2012-02-07 14:23:46 +00:00
Allan Jardine
5907eb4639
Docs: Fix - 8400 - mDataProp when null incorrectly suggested that sDefaultContent was an empty string. It is infact null. Also typo fixes.
2012-02-06 18:26:13 +00:00
Allan Jardine
ab9dfd5052
Fix: x-scrolling to the end of a table would cause the header and the columns to go out of alignment due to the header not being able to scroll as far as was needed (this was caused by the changes in 876a75f) - 8332.
...
Fix: Table could conitnually expand when x-scrolling was enabled. This was partly addressed in 6776, but the fix was incomplete as it would still occur on Safari Mac (possibly other browsers as well). This fix is very closely related to 8332 (hence commiting together as they are interdependent). Now use padding right on the header/footer wrapper to provide the overflow scroll ability, but only add it when a scrollbar is present - otherwise the width gets added on and we get the forever expanding table.
Dev: Unit tests - New tests for scrolling to ensure 6776 and 8332 don't occur again
2012-02-06 18:09:16 +00:00
Allan Jardine
0151d43c25
Fix: When fnPreDrawCallback is used to cancel a draw the processing display would remain active - this should not be the case as DataTables is now finished with its processing - 8371
2012-02-03 17:46:05 +00:00
Allan Jardine
de6482a15e
Fix: asStripClasses if given was being overruled by the default given for asStripeClasses - 8332
...
Fix: The extend function was only extending properties that existed on the original source object, not properties that only existed on the extender
2012-02-02 10:04:51 +00:00
Allan Jardine
92ce6487f2
DataTables 1.9.1 development begins
...
Fix: When using full numbers pagination in IE and clicking upon one of the numbers in the paging control, a Javascript error would occur due to trying to blur an element that was no longer in the DOM
2012-02-02 07:06:33 +00:00
Allan Jardine
2b126277fc
DataTables 1.9.0! :-)
2012-02-01 14:03:06 +00:00
Allan Jardine
1af3ebaf48
Fix: Docs: oSearch should be a namespace
2012-02-01 10:25:26 +00:00
Allan Jardine
7e18f3b484
Fix: Docs: fnVersion check should be marked with @type function
2012-02-01 09:53:39 +00:00
