Inconsistent email field state validity

[joseym]

It seems that the field state :invalid isn't always getting set for invalid emails.

see this fiddle: http://jsfiddle.net/joseym/bjpNy/

If you enter:

1. 👍 email@mail.com: Valid Form, Valid Field, No invalid state
2. 👍 email@mail.: Invalid Form, Invalid Field, Invalid state
3. 👍 email@mail.co: Valid Form, Valid Field, No invalid state
4. 👎 email@mail: Invalid Form, Invalid Field, no invalid state
5. 👎 email@mail.c: Invalid Form, Invalid Field, no invalid state

The user can get around this by mimicking their input:invalid classes or adding .ng-invalid to their invalid classes but it seems like the input states should correspond with the ng-invalid class that is applied to the input.

[btford]

As part of our effort to clean out old issues, this issue is being automatically closed since it has been inactivite for over two months.

Please try the newest versions of Angular (1.0.8 and 1.2.0-rc.1), and if the issue persists, comment below so we can discuss it.

Thanks!