From 378db26f465c0f2ee59f678ed9b35731bef9664f Mon Sep 17 00:00:00 2001
From: Peter Pavlovich <pavlovich@gmail.com>
Date: Sat, 1 Nov 2014 20:08:10 -0400
Subject: [PATCH] Handle default/no value supplied case for ngMaxlength
 directive

If one adds ng-maxlength="" to an input field, the default value of 0 for max length is used which results in an incorrect error being added to the input field. This fix checks for a value of 0 for the maxlength. If one uses this directive and purposefully supplies a value of 0 for the directive, that would make absolutely no sense in any scenario I can think of. By using this as the 'default' value (or the value used if a blank value is passed for this directive), and checking for that value and returning a result of 'valid' if that value is supplied, corrects this issue. This is not a problem for the ng-minlength directive as having a default value of 0 for the minimum length is actually a 'no-op' as you can't have a length less than 0.
---
 src/ng/directive/input.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/ng/directive/input.js b/src/ng/directive/input.js
index 1b393676cd79..029ff3fda0c5 100644
--- a/src/ng/directive/input.js
+++ b/src/ng/directive/input.js
@@ -2613,7 +2613,7 @@ var maxlengthDirective = function() {
         ctrl.$validate();
       });
       ctrl.$validators.maxlength = function(modelValue, viewValue) {
-        return ctrl.$isEmpty(modelValue) || viewValue.length <= maxlength;
+        return ctrl.$isEmpty(modelValue) || maxlength == 0 || viewValue.length <= maxlength;
       };
     }
   };