Column visibility 'at start' overrides state: columns_visibility - intended? #812

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

SafetyFast opened this issue May 21, 2021 · 0 comments

SafetyFast commented May 21, 2021

State (persistence) settings for column visibility are ignored for columns hidden 'at_start' by colsVisibility settings.

To reproduce *

Create a table with a hidden column 'x' (via the 'at_start' colsVisibility setting) and 'state: [columns_visibility: true]'.
Load the page; the column is indeed hidden.
Use the 'columns' drop-down to make column 'x' visible.
Reload the page.

Expected result *
Column 'x' remains visible; the state/persistence settings take precedence over the colsVisibility 'at_start' setting.
Observed result *
Column 'x' is hidden; the colsVisibility settings take precedence over the persistence (state) setting.

My guess is that this is the intended behavior, but I wanted to confirm that. If so, is there an option I've missed that would change that behavior?

Thanks for TableFilter, it is really a great tool and saved me a LOT of effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment