-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
TextBoxMask TextChanging event handler bug #3279
Comments
Hello oenarap, thank you for opening an issue with us! I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌 |
Thanks @oenarap for the report! If you have a fix, do you want to make a PR? |
Thanks @michael-hawker! PR would be fine with me. For the meantime though, changes i can make could be just a copy of my quick fix included in the bug report. It worked for me, but i'm sure you guys can come up with a better one. All best! |
hi @michael-hawker. any particular branch that i may be allowed to make a PR? |
@oenarap you can create a new branch of your own and we can merge that later in the master once the PR is approved 🙂 |
@oenarap not sure if you had a chance but once you have established all the changes in the forked branch then sync your PR with the main branch of WCT and feel free to submit the PR. Also, feel free to refer to the "Create/Submit the PullRequest" options in our new WIki page for any further guidance you may require. |
@oenarap please let us know of any updates. |
TextBoxMask TextChanging fix for #3279
TextBoxMask leaves an artifact (i.e., old Text value) when a new value is set. (in my case, thru data binding)
since this is just a subtle bug, please allow me to not comply with your required details for this report.
and let me get you directly where i found the offending part of the code:
1. within the if condition, textbox.Text will revert to old value even if you actually intended to assign a completely new/different value to it.
in the subsequent part of the same event handler:
2. the nested if condition will allow execution of the remaining part of the code which ends up in textbox.Text getting assigned with the old value, even if you actually intend to assign a null/emptly string to it.
here's the quick fix i came up with:
THANKS!
The text was updated successfully, but these errors were encountered: