fixed case that CHANGE was not triggered if the field loses focus with u...#91
Closed
viniciusoyama wants to merge 1 commit intoplentz:masterfrom
Closed
fixed case that CHANGE was not triggered if the field loses focus with u...#91viniciusoyama wants to merge 1 commit intoplentz:masterfrom
viniciusoyama wants to merge 1 commit intoplentz:masterfrom
Conversation
…h user clicking outside the field
Owner
|
Thanks @viniciusoyama. This is a know bug and as you find out, related to that "dirty" check. I think that we need to fix the whole problem, and your change fix just a few parts of it. Anyway, I will leave it open to use as a reference. |
Author
|
Hi. I didn't know that there was more problems related to this bug. I will see what I can do about this. Thanks for your help. |
Owner
|
I'm closing this one to centralize everything related to the change event problem in #44 |
This file contains hidden or 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.
Fixed a little bug:
If I change the field value and leave the field by clicking outside the field (not using TAB or ENTER) the CHANGE event was not triggered.