-
-
Notifications
You must be signed in to change notification settings - Fork 33.6k
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
Input Element Value Filter broken with 1.0.17 (works with 1.0.16) #2491
Comments
Might be related to this change: df01719 which was about fixing issues with debounced model data. |
I forgot: This issue was seen in Chrome v49. |
I can confirm this. I was just about to report it in. Just go to the docs, http://vuejs.org/guide/custom-filter.html#Two-way_Filters, and check for yourself. |
@swernerx My workaround so I dont have to put my production app back to 1.0.16:
|
Vue.js version
1.0.17
Steps to reproduce
We have developed an input component for formatted numbers (think currencies, percents) which does not work reliable anymore with the newest version. Sometimes it works, sometimes not. The issues happen when interacting with the input field e.g. changing the value in the running application. The filter has a read and write section to deal with parsing and formatting. The filter correctly sends out the changed value - but the formatted value itself does not seem to "reach" the input field. This is probably some timing / race condition issue as it works 50% of the time.
This is the markup of our component - see the
v-model
section about how we integrated the filter:This is how a typical filter looks in our application:
What is Expected?
It is expected that the input field always contains a formatted number when leaving/bluring the input field.
What is actually happening?
It is only formatted in about 50% of the cases. Sometimes it works. Sometimes not.
The text was updated successfully, but these errors were encountered: