ng-pattern binding is not working in v1.4

[aquisio]

I understand that v1.3 introduced some changes in the recommended usage of ng-pattern when the validation pattern / RegExp is exposed as a model property. This change is documented in the migration notes and works correctly in v1.3, as demonstrated in this JSFiddle.

However, using the same implementation in v1.4 does not work, as this JSFiddle shows. Instead, pattern validation always fails.

[gkalpak]

It doesn't actually have to do with ngPattern as much as it has to do with input[type="date"].

@aquisio: the 1.3.0-beta.8 version of Angular that you where using, didn't have support for date inputs, which means that they where treated as text inputs (i.e. reading the value from the input as the browser sets it). Per the spec, date input values are use the yyyy-MM-dd format, so ngPattern can match the string against the regex.
Now Angular has support for date inputs and has logic in place in order to convert the yyyy-MM-dd string value to an actual Date object. ngPattern tries to match the Date object to the regex (and fails).

@team (especially forms people): There seems to be a need for custom handling of pattern/ngPattern on date inputs (date, datetime-local, week, month).
We do this for min/ngMin and max/ngMax anyway.

[Narretz]

hm. ngPattern should probably only try to match the viewValue, not the modelValue. Because that's what pattern does.

[gkalpak]

Thinking about it again, you can't convert a regex to a date for comparing with the $modelValue :)

So, for the date input it does make sense for ngPattern to compare against the $viewValue.
(Not so sure about other inputs though, if that's what you meant.)