>Lots. But since I can't debug I don't know what the problem might be. Why not examine the HTML in the debugger and check that the attributes are being set.
>
>I can see that there is ng-invalid-max attribute shown when I inspect the control (and the red border is shown correctly). I'll try to see if there is any difference between the working page control and non-working page control when I inspect that control in Developer's Tools.
>
>This is working control
>
>

><input class="form-control percent-icon ng-not-empty ng-valid-min ng-valid-sm-number ng-dirty ng-valid-number ng-invalid ng-invalid-max ng-touched"
> id="discPct" max="100" min="-100" name="discPct" placeholder="0" ng-model="currentSpecial.discPct" type="number" 
>data-sm:number="" data-accuracy="0" style="">

>
>
>and this is not working
>
>

><input type="number" name="maxDaysLocal" id="maxDaysLocal" sm-focus="" min="1" max="45"
> ng-model="currentPrefs.loclccdays" 
>class="form-control ng-valid-min ng-valid-sm-number ng-not-empty ng-dirty ng-valid-number ng-invalid ng-invalid-max ng-touched" 
>placeholder="0" data-sm:number="" data-accuracy="0" style="">

Those look identical to me - apart from the obvious name/id and model changes. Look at the $error object for the input control in both cases.

Just a thought : you could use ng-messages/ng-message rather than the show/hide construct.