-
Notifications
You must be signed in to change notification settings - Fork 8
fix(textfield): validate on blur only #31
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
Conversation
|
Does that fix the issue you were running into? |
|
You need to add the blur event and do the update then? |
|
Or does the validate trigger the update call? |
Yes it fixes the bug where it was not possible to have in the textfield a string that could not represent a valid number, even if it was a step towards a valid value. For example "1." preceding "1.2" was not possible to type, due to the Now such sanitizing is done through
I don't understand what you mean.
|
Are we now missing the update call? Is it needed or not? |
We don't need it as long as the blur event is triggerred. This is why we settled on this simplification of validating inputs only at the end of the input, e.g. on blur. The same validation process is at work in both |
|
Should I merge? |
Remove update on update:modelValue to fix bug preventing typing non integer values in TextField Remove condition on dirty call in validate to replace the call in update Uniformize TextField template.html structure
24ddc75 to
e7cc48b
Compare
|
@jourdain I made new modifications. I removed the condition I also changed the This also fixes a bug we had with some TextFields where we could only type one character at a time, with a forced blur being trigerred after each one. |
|
@jourdain should we merge ? |
Remove update on update:modelValue to fix bug
preventing typing non integer values in TextField