-
Notifications
You must be signed in to change notification settings - Fork 400
Number Input is broken with Angular 1.3.3 #130
Comments
Thank you. This is great news that it'll be fixed (hopefully) in 1.3.4 :-) |
Hey @kentcdodds, Just wanted to let you know I just tested 1.3.4 and the number and maxlength issue is fixed. Bill |
👏 |
I am new to angular and formly, however I am using heavily angular formly. I will get stuck in ever new requirement.
|
your help is much appreciated if these things not get solved I need to write all the page in plain html with angular, which I don't want to do. Please help me. |
Hi @sucheendra, the best way to get help is to follow the instructions here: http://help.angular-formly.com For your first question, you'll simply set the For your second question, please go to that help link and create an example of what you mean. |
It helped Thank you Kent, Thanks & Regards, On Mon, Oct 5, 2015 at 11:08 AM, Kent C. Dodds notifications@github.com
|
In case others ran into this issue, I figured I'd post since it took a while for me to figure it out. Basically if you're running Formly with Angular 1.3.x the numeric inputs will not be updated to the ng-model because they are invalid. It seems that their ng-maxlength gets set to 0 by default. If you set an explicit value this fixes the issue, although it's not ideal.
This issue seems to be part of what Angular is doing (setting maxlength to 0 if it's null) along with how Formly is setting the maxlength (by default if maxlength is not specified, the attribute is still set to null). It should hopefully be fixed in 1.3.4, although I have not tested the PR yet.
Thanks,
Bill
Here is the link to the Angular pull request for 1.3.4:
angular/angular.js#9998
Example of what I'm talking about;
http://plnkr.co/edit/SJY6CofpRMhvPAo9hHpu
The text was updated successfully, but these errors were encountered: