-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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.36.0+] When minSpareCols is set to 1, using Tab key to create new columns deletes data from previous columns #4986
Comments
Thank you for sharing the issue @paolostyle Here is what I've got What is interesting is the fact that the data is saved properly when we use > (right arrow) instead. Gladly it doesn't happen for The bug has been created in the |
…dsontable#4986 (handsontable#5036) * Fix: minSpareCols should works with new selection transformation. handsontable#4986 * Added: test to prevent regression with selection and minSpareCols. handsontable#4986 * Reverted: unnecessary changes in core.setDataAtCell. handsontable#4986
Hi @paolostyle thank you again for sharing. |
I can't quite explain it, hence the rather bad title, so steps to reproduce:
minSpareCols: 1
is the most relevant optionIf you do that a few more times (type anything and press tab to create new column) you'll notice only the last typed value is being displayed. It does not happen when you use arrow keys but it's irrelevant - it should work with Tab too, considering there are no issues with adding new rows with Enter when
minSpareRows
is set to 1. I guess blocking Tab key for users or usingminSpareCols: 2
, in which case, interestingly, there's no such problem, is some kind of workaround, but regardless, it should be fixed.Handsontable version 0.38.1, bug occurs in at least latest Firefox, Chrome, Edge and IE11.
The text was updated successfully, but these errors were encountered: