-
Notifications
You must be signed in to change notification settings - Fork 45
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
type='number'
and value-as-number
#67
Comments
We tried adding Changing the type of Ideally, in a perfect world, what I would like to do is step away from this TLDR: I'd like to punt on this until we have a better solution. But it's in like my top 3 things to fix this quarter. |
@notwaldorf Replying a bit late (busy during this part of the year), but what issues are there with the suggested pull request? I have been using that in production for awhile now without any issues. The advantages are:
|
Gentle ping: given that Polymer cannot reliably perform 2-way binding on numeric inputs in IE/Edge, I think this bug deserves a higher priority. I can't even get 1-way binding of numeric inputs working reliably with |
What if instead of numeric input we offered a generic value transform function? That feels like a natural extension of Update: moved this suggestion to a new ticket. |
Any updates? I am facing the same issue. |
I'm going to close this issue since I don't think it will ever be implemented |
So, right now
bind-value
always returns astring
. There are two ways this could be fixed:value-as-number
property (which would still allow two way binding to thevalue
)value
aNumber
iftype
is set toNumber
Personally I vote for the second option, but I would love to see this fixed.
The text was updated successfully, but these errors were encountered: