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

[BUG] one time binding doesn't deal with null like value properly #2988

Closed
dsonet opened this issue May 31, 2016 · 2 comments
Closed

[BUG] one time binding doesn't deal with null like value properly #2988

dsonet opened this issue May 31, 2016 · 2 comments
Labels
bug in progress

Comments

@dsonet
Copy link
Contributor

dsonet commented May 31, 2016 •
edited

Vue.js version

1.0.24

Reproduction Link

http://jsbin.com/yesozewezu/1/edit?html,js,output

Steps to reproduce

For one time binding, undefined value would display as "undefined", it's different from two-way binding.

What is Expected?

Should display as empty.

What is actually happening?

Display undefined.
dsonet added a commit to dsonet/vue that referenced this issue May 31, 2016
@dsonet
Fixed vuejs#2988
6bc7c80 
Fixed the incorrect rendering of undefined value in one-way binding mode.
dsonet added a commit to dsonet/vue that referenced this issue Jun 1, 2016
@dsonet
Fixed vuejs#2988
b3148cf 
Fixed the incorrect rendering of undefined value in one-way binding mode.
@LinusBorg
Copy link
Member

Hello @dsonet,
Thank you very much for this report. We will continue this in your pull request #2989

@dsonet dsonet changed the title [BUG] one time binding may cause display "undefined" [BUG] one time binding doesn't deal with null like value properly Jun 2, 2016
@dsonet
Copy link
Contributor Author

dsonet commented Jun 2, 2016 •
edited

Hi @LinusBorg FYI. Just updated the reproduction case, also new fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug in progress
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dsonet @LinusBorg