<v-text-field> mask doesn't work when combined with .number modifier #2137
Assignees
Labels
T: bug
Functionality that does not work as intended/expected
Comments
azaars
added a commit
to azaars/vuetify
that referenced
this issue
Oct 11, 2017
- Dev should be allowed to set input to null and expect v-model to retain the null value. Requesting a reconsideration against returning a string as in commit 95b7f83 - Handle v-model.number modifier correctly. Whether the input is string, number or null, the resulting emit() should return the same type or null. Requesting this as an alternative to resolve vuetifyjs#2137. - Handle input of type number. Likewise, the resulting emit() should return the same type. Requesting this as an alternative to resolve vuetifyjs#2136.
johnleider
pushed a commit
that referenced
this issue
Oct 18, 2017
* Bug fixes on v-text-field 1. Resolves #2057 2. Resolves #2096 3. Resolves #2097 * Make way for props.clearable=true * Removes unneeded sanity check. * null check on externally set value * Add conditional setSelectionRange() & anticipate valid null value. * Allow null value & v-model.number config + handle input of type number - Dev should be allowed to set input to null and expect v-model to retain the null value. Requesting a reconsideration against returning a string as in commit 95b7f83 - Handle v-model.number modifier correctly. Whether the input is string, number or null, the resulting emit() should return the same type or null. Requesting this as an alternative to resolve #2137. - Handle input of type number. Likewise, the resulting emit() should return the same type. Requesting this as an alternative to resolve #2136. * Clean up codes involving conditional mask Fix #2158 * Removes redundant check on oldValue (input.value) * Removes useless getLazyValue() * Post-review updates & fixes - Revert to last commit to undo unnecessary changes - Fix computed.inputValue to account for type of emitted value - Enhance watch.value to check for external/internal change - Prevent resetSelections() from causing runtime error when type="number' - Fix multiple emits bug - Minor change to local variable names to be consistent between functions
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Steps to reproduce
Versions
0.16.4
What is expected ?
The text field should display '12.34'
What is actually happening ?
The text field is not formatted and the console in devtools shows errors.
Reproduction Link
https://codepen.io/bspg/pen/aLKybz
The text was updated successfully, but these errors were encountered: