-
Notifications
You must be signed in to change notification settings - Fork 3k
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.
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
[0.31.0+] Disabling the colHeaders
property using updateSettings
doesn't work.
#4136
Labels
bug
Core: Update settings
Plugin
Headers
Regression
Issues that were created while adding new changes to the source code
Status: Released
Milestone
Comments
I think header management doesn't work properly since 0.29.0: http://jsfiddle.net/k2gdhdcy/ |
The issue is replicable in v0.35.0 as well |
v from v from v |
colHeaders
property using updateSettings
doesn't work.colHeaders
property using updateSettings
doesn't work.
mrpiotr-dev
added a commit
that referenced
this issue
Jan 5, 2019
1 task
mrpiotr-dev
added a commit
that referenced
this issue
Jan 7, 2019
mrpiotr-dev
pushed a commit
that referenced
this issue
Jan 17, 2019
jansiegel
added a commit
that referenced
this issue
Feb 22, 2019
jansiegel
added a commit
that referenced
this issue
Feb 22, 2019
* Partially revert changes from #4136. (#5807) * Add a test case for #5807. * Increase sleep time for the test case. #5807 * Add headers to the test case #5807 * Change data for the test case #5807 * Modify the test case. #5807 * Apply suggestions from code review Co-Authored-By: jansiegel <jansiegel@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Core: Update settings
Plugin
Headers
Regression
Issues that were created while adding new changes to the source code
Status: Released
Description
When trying to disable the
colHeaders
property by using theupdateSettings
method, the column headers don't get removed. Instead, we're left with a non-functional, not scrollable header bar at the top of the table, covering the first data row.Seems to happen since
0.31.0
Steps to reproduce
Your environment
The text was updated successfully, but these errors were encountered: