Skip to content
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

change from 1.0.11 to 1.0.12 have problem #2068

Closed
iLexN opened this issue Dec 22, 2015 · 2 comments
Closed

change from 1.0.11 to 1.0.12 have problem #2068

iLexN opened this issue Dec 22, 2015 · 2 comments

Comments

@iLexN
Copy link

iLexN commented Dec 22, 2015

when i upgrade the vuejs from 1.0.11 to 1.0.12 , my app is going wrong.

here is the example :
1.0.11 : http://jsfiddle.net/5sH6A/236/
1.0.12 : http://jsfiddle.net/5sH6A/237/

the main different is the data cannot load to the input box when the app create.

  • 1.0.11 the data can show in the input box correctly
  • 1.0.12 the data is empty in the input box , and also update the data to empty(cos the input box is empty ?)

also try changed the 'ready' to 'created' ,
1.0.11 : http://jsfiddle.net/5sH6A/238/
1.0.12 : http://jsfiddle.net/5sH6A/239/
the result is also not the same.

i guess , the v-model in the input field
1.0.11 the data show in the v-model input field
1.0.12 the v-model updated the data

i may be doing in the wrong way , need some suggestion.

many thank
please forgive my poor engish.

@iLexN iLexN changed the title change from 1.0.11 to 1.0.12 change from 1.0.11 to 1.0.12 have problem Dec 22, 2015
@simplesmiler
Copy link
Member

Boiled it down to: https://jsfiddle.net/simplesmiler/2z9mL2f5/
This will probably get fixed, but here is a few recommendations:

  • Use v-bind:attribute="expression" instead of attribute="{{ expression }}" unless you have a good reason.
  • Do not use value attribute alongside v-model directive.

@iLexN iLexN closed this as completed Dec 23, 2015
iLexN added a commit to iLexN/KS-Car that referenced this issue Dec 23, 2015
@Vorror
Copy link

Vorror commented Dec 23, 2015

Why close it? Shouldn't this issue still get looked at? Especially if it worked in a previous build?

@yyx990803 yyx990803 reopened this Dec 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants