Do not update undoValue in applyInputValue. #2757 #2758
Closed
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
- Instead rely on update of undoValue in blurEvent.
- Inputmask does not recognize a change from null to 0 because undoValue and nptValue is never null. Hence a change event must always be emitted on '0.00'. - Another approach but way more labor-intensive would be to save null value.
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.
This is the proposed fix for #2757.
Please scrutinize if
inputmask.undoValue = nptValueand$input.trigger("change");is executed whenever it is needed.I am not sure if in every situation all conditionals of blurEvent are truthy and if it is possible to dodge blurEvent altogether.