adammessinger/flexitable

A jQuery plugin for responsive tables with column toggling. Performant for even very large tables.

flexitable's Issues

Feature request: save column visibility state

It would be great it there was an option to save the state of the columns (I assume either via localstorage or cookies, or maybe store.js).

When printing, columns hidden by user shouldn't print

Currently, some CSS inside an @media print block makes all columns visible in the print-out. It's causing confusion for some users when the thing on the page doesn't match the column selections they've made on screen.

In Safari 9, responsive features cause profound slowdown of plugin initialization

The problem is with the class names added to cells based on their column header's data-flexitable-priority-class attribute. Class name manipulation is a little slower in Safari 8 than other browsers, but profiling in version 9 indicates cell class changes now trigger layout recalculations that can stretch init time to > 1 minute for very large tables.*

Possible fix: adding a data attribute to the cells rather than a class doesn't cause these problems in Safari 9, but could still be used in selectors for responsive media queries.

Users can currently work around this with the new lazy column cache feature, which disables responsive column hiding. Do this by passing lazy_column_caching: true when calling the plugin.

*About 140K cells in my test case, and this was on a 2009 Mac mini. YMMV depending on equipment.

Destroy Method Should Show All Hidden Columns

Any columns toggled "off" by the plugin should be shown by .flexitable({ destroy: 'toggle' }).

_updateProgressMeter() throws error if use_toggle_button option is false

Function should exit early if user is trying to use only the responsive column feature by turning the toggle button off.

If Flexitable was run with init_toggle_on_button_click option set to true, can't destroy

In this case, running $('table').flexitable({ destroy: 'toggle' }) does nothing until the column toggle button is clicked and the plugin gets fully initialized. The fault appears to lie in the viewmodel never getting stored with the table if lazy init is used.