0
I Use This!
Low Activity

Commits : Listings

Analyzed about 16 hours ago. based on code collected 1 day ago.
May 23, 2023 — May 23, 2024
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
Update copyright message More... over 11 years ago
JSHint fixes More... over 11 years ago
Update - dropping support for IE6/7 - IE8 is still supported and works fine. More... over 11 years ago
Update: Improvements to the fnRedrawLayout method for 2.5.0 - will not 'regrab' the column sizes from DataTables, apply them and redraw the layout when fnRedrawLayout is called. More... almost 12 years ago
Dev - fix: Add the DataTables Bootstrap integration JS to the bootstrap example. It isn't stricktly needed here, since it is mainly about the pagination, but it is proper to have it here, and it does include the full layout in sDom for Bootstrap More... almost 12 years ago
Dev: Remove FixedColumns CSS reference from the bootstrap example, the bootstrap integration file has it all More... almost 12 years ago
Merge branch 'master' of github.com:DataTables/FixedColumns More... almost 12 years ago
New - example: Twitter Bootstrap integration with FixedColumns More... almost 12 years ago
New: When using sAjaxSource in DataTables with FixedColumns, you used to need to put the FixedColumns initialisation into fnInitComplete - however, that's rather non-obvious and a pain even when you do know. FixedColumns will now detect this situation and hook into the DataTables events automatically, so FixedColumns can now be declared consecutively as would be expected in all cases. Update - example: Server-side processing example updated to remove the use of fnInitComplete since that is no longer needed. More... almost 12 years ago
Merge pull request #3 from johnhaitas/master More... almost 12 years ago
patch to improve interaction with Scroller plugin when scrolling More... almost 12 years ago
Dev fix: The height of the wrapper for the header, footer and body needs a different height calculation than the height of hte body alone! More... almost 12 years ago
Updated: The markup for the left column is not subjected to the same treatment as the right - i.e. it is not used at all if not needed. This addresses a rendering issue in Safari as well where the left scrollbar could be hidden in right fixed column tables. More... about 12 years ago
Dev: Code style for the example More... about 12 years ago
Moving on to 2.5 development Significant update in therms of how FixedColumns operates - no longer will it set the column visbility for the columns to be fixed, and instead just places the fixed columns on top of the target columns (similar to how FixedHeader works). The grid layout has been updated to allow for this. New: The fixed columns can be used for scrolling! Both x-scrolling (which works using the mousewheel event) and y-scrolling (which is natural scrolling) will work now, which will make the interaction a lot less confusing for end users. New: The scrollbar when fixing a right column is no longer in the middle of the table (which is the main reason for changing the column vibility method to the new overlay) - it is now where you would expect on the right of the table. More... about 12 years ago
Fix: FixedColumns wasn't taking into account that there can be TH elements in the TBODY these days in DataTables - thus is was skipping TH elements when calculating the widths to apply to the frozen columns, resulting in the sizes applied bying shifted by the number of TH elements used in the row. The fix is to use a selector that also pulls in TH elements. We could use the DataTables internal method _fnGetTdNodes (and ultimatily that will be the best thing to do), but for the moment we modify the selector to retail DT1.8 compatibility for FixedCOlumns. More... about 12 years ago
Fix: Columns should have the inner width applied to them, while the grid boxes need the outer widths - 9744 More... about 12 years ago
Fix: When cloning the inner header element for the scrolling body table (the hidden column) we were working directly with the header cell for the column, rather than a clone. This meant that we were amnipulating the 'real' header, rather than a throw away clone, resulting is all sorts of problems when trying to access the real header later on - 9596 More... about 12 years ago
2.0.3 release More... about 12 years ago
Fix: Change to how the column widths are matched - apply the width from the DataTable calculation equally to both the header and body. Overcomes cross browser issues with width and outerWidth More... about 12 years ago
Fix: Column width matching should use outerWidth More... about 12 years ago
Fix: the column width could be applied incorrectly when using multiple fixed columns - the problem was that although the clone had a thead element in it, there were no cells in it - hence the browser was getting confused that hte body had two columns while the header had none and it would pick to spread the column widths equally. The fix is to put the header cells in, just like how DataTables does it More... about 12 years ago
Move on to 2.0.3 development Fix: When the header (or footer) has multiple rows in it, or col/rowspan, the class copy could copy to the wrong cell - 2815 - the fix is to use the DataTables detect header function and get a layout array with 1:1 mapping between the fixed column and the real DataTable and the copy the classes across. More... over 12 years ago
Example - fix: Column indexes were updating the visible column in the table, where as we only want to update the first column data index (i.e. the hidden column that is it he fixed column) - 8499 More... over 12 years ago
2.0.2 development complete More... over 12 years ago
Fix: Fix function call typo More... over 12 years ago
Fix: Row height matching should be applied to the thead and tfoot, regardless of what the sHeightMatch parameter is - otherwise we don't stand a chance of getting rowspan thead cells to match More... over 12 years ago
Fix: Same issue with heights in IE8... More... over 12 years ago
Fix: IE9 wasn't correctly aligning fixed columns - apparently it need to work the same way as all the old browsers. Its a bit messy this (trial and error really) with the high matching, but it seems to be working... More... over 12 years ago
Wrap up 2.0.1 development More... almost 13 years ago