Fixed an issue with the keyboard navigation when there are hidden columns #1893
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @AllenFang, thank you for the amazing library, I love it!
It looks like there is an issue with keyboard navigation in 4.3.1 when there are hidden columns. To replicate it you can create a table with any of the columns hidden and keyboard navigation enabled. It looks like you planned for it by adding the visibleColumnSize variable, but variable 'x' still contains absolute column number.
What I did, is added an visibleColumnIndices array with indices of the non-hidden columns and made 'x' take only values from it.