This repository has been archived by the owner on Apr 28, 2020. It is now read-only.
Fix cellIndex data bug #6
Open
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
|
Ou thanks. I havent noticed this. Will look into it tomorrow. Honestly it is very possible that there are bugs. We dont use it that much. For example multiple tablexes on one page are almost untested. |
|
I have multiple tables on one page, and due to the field name key, they work very well without getting into each other's way. So that is not a problem. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Seems to be a bug in this plugin due to the cellIndex not being set for each input field.
This was causing some strange behaviour in the field. Has anyone else run into this issue?
Before
After