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.

Sign up for GitHub

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

Jump to bottom

v-model incorrect behavior with 'undefined' value #1528

Closed
andrei-kochetygov opened this issue Jul 6, 2020 · 0 comments · Fixed by #1530
Closed

v-model incorrect behavior with 'undefined' value #1528

andrei-kochetygov opened this issue Jul 6, 2020 · 0 comments · Fixed by #1530

Comments

@andrei-kochetygov
Copy link

andrei-kochetygov commented Jul 6, 2020 •
edited
Loading

Version

3.0.0-beta.18

Reproduction link

https://flatdragon.github.io/vue-next-v-model-incorrect/

Steps to reproduce

  1. Check block labeled "Input value" to see correct 'undefined' conversion to empty value.
  2. Check neighbour input to see text 'undefined' instead of empty value.

What is expected?

'undefined' should no appear as text value on input.

What is actually happening?

'undefined' is appear as text value on input.

See Vue 2 v-model behaviour on GitHub Pages (Source code).
See Vue 3 v-model behaviour on GitHub Pages (Source code).
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(v-model): keep the same behavior as v-model with undefinedvalue with 2.x underfin/vue-next
1 participant
@andrei-kochetygov