Skip to content

<textarea>'s placeholder becomes its value inside <template> in IE10 #760

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
Closed
fullfs opened this issue Mar 31, 2015 · 6 comments
Closed

<textarea>'s placeholder becomes its value inside <template> in IE10 #760

fullfs opened this issue Mar 31, 2015 · 6 comments

Comments

@fullfs
Copy link

fullfs commented Mar 31, 2015

Hello!
http://jsfiddle.net/4ty2v4fc/65/

Edit:
It fails without v-repeat too:
http://jsfiddle.net/4ty2v4fc/66/
@young-steveo
Copy link

@fullfs It's not happening for me in Chrome 41.

@fullfs
Copy link
Author

fullfs commented Mar 31, 2015

@young-steveo yep, it's not. Check out the subject, please :) It occurs in IE10 (probably IE11 too).

@young-steveo
Copy link

@fullfs Whoops. Missed that, sorry.

@liuyanghejerry
Copy link

A quick search shows that there is a fixed related issue before: https://github.com/yyx990803/vue/issues/558 .

I traced a while and found this issue may come from here: https://github.com/yyx990803/vue/blob/master/src/parsers/template.js#L131

When textarea is a child of template and a placeholder is set, the textarea already contained text which is actually its placeholder. And Vue doesn't handle this situation.

Wish it helps a little to this issue.

@fullfs fullfs changed the title <textarea>'s placeholder becomes its value inside v-repeat on <template> in IE10 <textarea>'s placeholder becomes its value inside <template> in IE10 Apr 1, 2015
@fullfs
Copy link
Author

fullfs commented Apr 1, 2015

@liuyanghejerry great work gathering the information, thanks!
By the way, when using v-attr="placeholder: " everything works fine (no wonder).

@liuyanghejerry
Copy link

@fullfs That's right. I guess this is the workaround for now.

yyx990803 added a commit that referenced this issue Apr 18, 2015
@yyx990803
use clone instead of stringToFrag for normal node in template parser (f…
de3b59f 
…ix #760)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@liuyanghejerry @young-steveo @yyx990803 @fullfs