Allan Jardine
acf989695e
Fix: $.fn.dataTable.ext.pager.numbers_length was not taken into account when showing ellipsis on both sides of the current number in the paging controller
...
Fix: Ellipsis elements didn't have padding which could be jarring when shifting between paging that does and doesn't show ellipsis
This fixes DataTables/DataTables #26
2015-04-03 14:16:33 +01:00
Allan Jardine
cbb5a5d6e9
Fix: dt-init row().child() couldn't accept an array of jQuery objects
...
See https://www.datatables.net/forums/discussion/26441 for details
2015-04-03 12:21:50 +01:00
Allan Jardine
5c919423c1
Fix - docs: dt-api row().child() notes that className is not added to pre-existing node
2015-04-03 12:21:27 +01:00
Allan Jardine
565b639c34
Fix: Scrollbar width wasn't correctly detected in IE9
...
Fix: Scrollbar width was being calculated everytime requested on machines with zero width scrollbars
The scrollbar width calculation method has been rewritten to use a
single element with use of `offsetWidth` and `clientWidth` to calculate
the scrollbar width. This works all the way back to IE6.
2015-04-03 12:12:15 +01:00
Allan Jardine
220ae99e08
Updated: Extend currency support to include all top 20 internationally traded currencies. This includes the Russian ruble, South Korean Won, Turkish Lira, India Rupee, Brazilian real, South African rand, Swiss franc, Swedish korona, Norwegian krone and Danish krone.
...
Any additional currancies should be added as a plug-in, not to the core!
Fixes DataTables/DataTablesSrc #38
2015-04-03 10:45:41 +01:00
Allan Jardine
294a32f8d0
Fix docs: Add reference to dt-init columns.orderSequence from dt-init order
2015-04-03 09:50:06 +01:00
Allan Jardine
e0f2cfd81e
Fix: When holding shift and clicking on a single sorted column it was possible to attempt to remove the sort (the internal sorting array was []). This shouldn't be possible, and now isn't.
...
* This fixes DataTables/DataTables #526
2015-03-31 20:05:23 +01:00
Allan Jardine
1e10603810
Fix: Update numebr render to return the original data point if the data passed in is not a number or a string. This allows dt-init columns.defaultContent to be used.
2015-03-20 10:49:34 +00:00
Allan Jardine
7851a6a204
Fix: If async:false is used in the Ajax configuration, callbacks assigned with dt-api ajax.reload() would not trigger until another draw has been executed.
...
This was due simply to the code ordering for how the callback is
triggered. See https://www.datatables.net/forums/discussion/26474 for
more information.
2015-03-19 16:20:34 +00:00
Allan Jardine
79f969ef58
Fix: dt-api $.fn.dataTable.isDataTable() could give incorrect results if a table did not have scrolling enabled
2015-03-18 16:53:25 +00:00
Allan Jardine
2ee5b3e7f6
New: dt-api init() method for plug-in developers to get the initialisation options configured for the DataTable
2015-03-18 16:53:07 +00:00
Allan Jardine
9896d0295d
Fix: If the thead contained a table the selector that was looking to find the first row in the table was selected the row from the header table rather than the tbody. This could cause errors such as HTML5 data-* attributes not being detected.
...
This fixes DataTables/DataTables #508
2015-03-12 10:29:16 +00:00
Allan Jardine
825877f157
New: dt-api rows().every(), dt-api columns().every() and dt-api cells().every() iterator methods to make it easier to perform operations on the table elements. This is done by setting the context of the callback provided to be the singular expression for the table elemtn in question. This basically means you can access the singular methods from this - e.g. this.data() will get the data for the element, this.node() will get the cell when using dt-api cells().every() etc. The exisiting interator methods of dt-api each() and dt-api iterator() remain, and each has its own place for optimial usage of the API, but it is likely that the majority of use will switch to focus on these new methods. The examples in the rest of hte documentation has been updated to reflect this fact.
2015-03-03 15:42:36 +00:00
Allan Jardine
0942fa38a6
Fix: dt-api cells() when given a selector options object in the first parameter was incorrectly applying the selector for the cells.
2015-03-03 15:42:22 +00:00
Allan Jardine
7ef92e4f56
Fix: The initalisation object was being cloned on init which could cause a major performance hit if you pass in a large data set into dt-init data. The table node and internal API reference also should not be cloned.
...
* Thank you to B Lyon for spotting this issue and writing it up:
http://www.nowherenearithaca.com/2015/03/avoiding-performance-gotcha-with-jquery.html
2015-03-02 13:25:51 +00:00
Allan Jardine
16c48ad4bf
Fix: dt-event xhr was not being emitted when dt-init ajax was being given as a function
2015-02-27 15:12:46 +00:00
Allan Jardine
ee9ca0336e
Fix: Scrollbar left detection wasn't allowing for sub-pixel rendering which occurs when browsers are zoomed
...
* This refers to DataTables/DataTables #479 and DataTables/Scroller #44
2015-02-27 12:00:43 +00:00
Allan Jardine
b1ff92a274
Fix: Error in the detection of style="width:..." attributes. DataTables was reading the pixel value that it had written if the columns were recalculated. Now only percentage values are used from the style width.
...
* This fixes DataTables/DataTables #501
2015-02-25 10:48:22 +00:00
Allan Jardine
c6be28ef8f
Call _fnAjaxDataSrc before setting recordsTotal
...
_fnAjaxDataSrc will in turn call _fnGetObjectDataFn, which
can be specified by the dataSrc method.
This way the dataSrc can set the recordsTotal parameter on
the json data and the changes will be read into the
recordsTotal/recordsFiltered variables.
2015-02-19 13:38:14 +00:00
Allan Jardine
62da8efbca
New: The dt-init ajax.data option, when used as a function, now has the DataTables' settings object passed in as the second parameter, which can be useful to access the API if needed
2015-02-19 13:37:57 +00:00
Allan Jardine
a1458bf80c
Fix: Legacy API fnDraw was incorrectly handling the case when false was passed in.
...
* See DataTables/DataTables #499
2015-02-17 15:00:24 +00:00
Allan Jardine
b433f105a3
Fix: Due to use of an HTML entity, DataTables could fail on XHTML pages
2015-02-17 10:29:09 +00:00
Allan Jardine
f1b561ec53
Fix: dt-init columns.orderData wasn't working if given as an integer
2015-02-12 14:11:37 +00:00
Allan Jardine
15991a26eb
Dev: 1.10.5 version
2015-02-12 14:11:18 +00:00
Allan Jardine
6fbd6a9c46
Dev: Firebase database in example documentation rather than AIR (outdated)
2015-02-12 14:10:38 +00:00
Allan Jardine
2c67caad44
Fix: Exit out of the extend API method if possible, for performance
2015-02-10 14:26:37 +00:00
Allan Jardine
34fb1cb18a
Dev: Add buttons object to .ext for future buttons extension
2015-02-10 14:25:57 +00:00
Allan Jardine
c98854def4
Fix - example: Dro the http protocol from the i18n CDN file loder example so it works over https
2015-02-10 14:25:16 +00:00
Allan Jardine
d6f46dffbb
New: DataTables intialisation options can now be specified using HTML data-* attributes on the HTML <table> tag and on the cells of the column headers in the table.
...
* A new example of this is included
* Fixes DataTables/DataTablesSrc #9
2015-02-06 16:35:34 +00:00
Allan Jardine
4039e77a6f
Fix: In IE9 where the table is in an iframe paging elements were not added until after the first draw
...
* See thread 23915 for details and kudos to helenm for the research into the issue
2015-02-04 16:11:59 +00:00
Allan Jardine
7a26c5d4c8
Fix: When detecting is the table has a width attribute we can also use style.width to check if a width as been assigned using the style attribute. This doesn't work for reading CSS assigned information, that would require parsing the stylesheet` but it does mean there is a way of doing this with using deprecated attributes.
2015-02-04 10:55:43 +00:00
Allan Jardine
c7e18c4236
move eq jQuery selector outside of selector
2015-01-22 10:21:30 +00:00
Allan Jardine
d65dd47fe6
New: where condition controls for the example PHP server-side processing class (SSP). This takes the form of a new complex method (to compliment the exisiting simple method) which accepts where parameters that can be used for either user based filtering, or server based filtering.
2015-01-11 16:26:59 +00:00
Allan Jardine
be061edb7b
Dev: Remove accidentally committed debug
2014-12-22 17:14:02 +00:00
Allan Jardine
7c07b80222
New: Improved error handling - $.fn.dataTable.ext.errMode can now be:
...
* `alert` - Alert the error
* `throw` - Throw an error
* `none` - Do nothing
* A function that is called
New: `dt-event error` event that is triggered when an error occurs (regardless of the value of `$.fn.dataTable.ext.errMode`
2014-12-22 16:15:10 +00:00
Allan Jardine
1c95f9fe06
Dev: Remove debug
2014-12-15 15:46:24 +00:00
Allan Jardine
25ceef46ab
Fix: When initialising a table and checking it it already exists, we should check against header and footer elements as well, so they can be used as the selectors
...
This fixes DataTables/DataTables #467
2014-12-15 15:13:08 +00:00
Allan Jardine
90ce3773f5
Fix: When detecting HTML5 attributes need to check for null from getAttribute, since otherwise empty strings would fail.
...
See thread 24802
2014-12-02 10:37:40 +00:00
Allan Jardine
31670cc1c5
Fix: dt-api $.fn.dataTable.isDataTable() wasn't working correctly on scrolling tables when the header or footer table was passed in
2014-11-24 10:51:01 +00:00
Allan Jardine
cb957c019e
Merge pull request #22 from bjmiller/master
...
Fix for CommonJS/Browserify
2014-11-18 17:10:50 +00:00
Allan Jardine
cd2423d21a
Fix #23 : Attach the scroll event for the header alignment using the DT namespace to ensure that it is removed on destroy
2014-11-18 17:10:34 +00:00
Allan Jardine
dd7fbeb0a7
Fix for CommonJS/Browserify
...
I'm not sure whether this breaks any other CJS implementation, but the only one you're likely to have to worry about is Browserify.
This relates to https://github.com/DataTables/DataTables/issues/434
2014-11-18 17:10:18 +00:00
Allan Jardine
3a22a082c3
New: DT_RowAttr special parameter for row data to be able to set abstract parameters for the row. This compliments the exisiting DT_RowId, DT_RowClass and DT_RowData parameters.
...
Thanks to Jifer in thread 24534 for this suggestion
2014-11-12 10:09:17 +00:00
Allan Jardine
d83f47cfb5
Fix: dt-api $.fn.dataTable.util.throttle() was missing the first call.
...
Dev: Moving on to 1.10.5-dev
2014-11-11 14:14:11 +00:00
Allan Jardine
06c1cbebde
DataTables 1.10.4 release
2014-11-07 15:17:44 +00:00
Allan Jardine
9841c3f038
Dev: Fix return case for column visiblity:
2014-11-07 15:17:29 +00:00
Allan Jardine
f4d1495a2c
Dev: Tests for the cell invalidation update
2014-11-07 15:17:14 +00:00
Allan Jardine
24761003f3
Fix: dt-api cell().invalidate() and dt-api cells().invalidate() now invalidate only the cell(s) in question and not the whole row.
...
Previously the whole row was invalidated as a quick workaround for what
I would would be a complex task, but the solution is actually relatively
simple and small in code size, reusing much of the current invalidation
code. The cache data for the whole row is still removed, but the
important part of minimising the DOM interaction is in place.
2014-11-07 12:28:44 +00:00
Allan Jardine
fb6a7be880
Fix: Selector errors when using jQuery selectors with dt-init deferRender enabled
...
Fix: Incorrect returns from sub-methods if a selector does not contain any results (DataTables/DataTables #431 )
Update: `dt-api iterator()` has a fourth parameter to indicate that a return value is expected
The basic issue here was the `iterator()`'s automatic check to see if a
new API instance should be returned or not. If there are no results from
a selector the iterator will just use the original API instance to
return, but this isn't correct as we expect an empty result set in this
case. This is partly due to the fact that the top level methods (`row()`
for example) will return 2D arrays, while the child methods will flatten
the results, this is parhaps an error in the API, but too late to fix
now.
To address this, `iterator()` now has a parameter to tell it if a new
instance should be used or not. I debated about a new method
`iteratorNew()`, but I think this is just as clear (which isn't very
clear unfortunatly, but just needs to be made clear in the
documentation, which I've updated for this change).
I've added tests for the selectors with `deferRender` enabled. The test
suite is still in desperate need of update...
2014-11-03 15:18:18 +00:00
Allan Jardine
e92582b45a
Fix: Page length change will now attempt to keep the start point on the current page, but will shift that row's position away from the start point, so that the paging is always consistent in its display. Without this changing the page length could result in landing on page "1.4" (or some other partial page) that you could never get to with just paging alone. That is no longer possible in DataTables.
...
This is something that has been in DataTables since the version first
vresion and was contentious at that point so while this is a minor code
change, for me it is quite a big change! I feel that this is the correct
operation now, although it does result in rows being moved around where
they might not be needed to if partial pages could be used.
2014-10-30 15:15:20 +00:00
