We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Hello,
thank you for providing ColReorder!
OCA.Analytics.tableObject = new DataTable(domTarget, { colReorder: { order: [0, 2, 1, 5, 6, 4, 3]} })
OCA.Analytics.tableObject.destroy();
OCA.Analytics.tableObject = new DataTable(domTarget, { colReorder: true })
OCA.Analytics.tableObject.colReorder.reset()
reordered table:
normal table after coming from the reordered one:
The text was updated successfully, but these errors were encountered:
I want to add some additional finding for documentation purposes.
I use the parameter scrollX: true. if this is removed, the tables is generated correctly with colReorder: true
scrollX: true
colReorder: true
but why does it work with a completely clean table, but not with a redrawn, once it was colReordered before?
Sorry, something went wrong.
Could you create a test case demonstrating the issue please? I've just tried to do so here: https://live.datatables.net/hudumofu/1/edit but it appears to work as expected.
No branches or pull requests
Hello,
thank you for providing ColReorder!
OCA.Analytics.tableObject = new DataTable(domTarget, { colReorder: { order: [0, 2, 1, 5, 6, 4, 3]} })
OCA.Analytics.tableObject.destroy();
OCA.Analytics.tableObject = new DataTable(domTarget, { colReorder: true })
OCA.Analytics.tableObject.colReorder.reset()
before the destroy does not make a difference. something seems to be kept in memory somewhere?reordered table:
normal table after coming from the reordered one:
The text was updated successfully, but these errors were encountered: