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

[2.0] v-once and v-for don't seem to play nice together #3155

Closed
phanan opened this issue Jun 26, 2016 · 0 comments
Closed

[2.0] v-once and v-for don't seem to play nice together #3155

phanan opened this issue Jun 26, 2016 · 0 comments
Labels
bug

Comments

@phanan
Copy link
Member

phanan commented Jun 26, 2016

Vue.js version

2.x

Reproduction Link

https://jsfiddle.net/0jjufkpb/

Steps to reproduce

Just run the fiddle.

What is Expected?

arr is iterated, each item and its type (string) are displayed.

What is actually happening?

Items are lost (typeof returns undefined).

Will look deeper into this. If @yyx990803 could give a hint – or clarify that this is the expected behavior somehow – that would be great.
@phanan phanan changed the title [2.0] v-once and v-for doesn't seem to play nice together [2.0] v-once and v-for doesn't seem to play nice together Jun 26, 2016
@phanan phanan changed the title [2.0] v-once and v-for doesn't seem to play nice together [2.0] v-once and v-for don't seem to play nice together Jun 26, 2016
yyx990803 added a commit that referenced this issue Jun 27, 2016
@yyx990803
fix v-once with v-for and remove unused _t method (fix #3155)
cf8aedd
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yyx990803 @phanan