ngMessages have multiple bugs

[gligoran]

Hello,

I've created a pen, with multiple cases where ngMessages don't work as they should.

There seem to be 2 core issues:

1. The auto hide functionality (ngMessages that doesn't use md-auto-hide, ngIf, ngShow, or any other directive that disables auto hide) has trouble switching between different errors.
2. Custom $asyncValidators display multiple of the same message at once.

[jaGarcia]

+1 to point 1

[jaspersorrio]

+1 to point 1 & 2

Here is my pen!

I noticed if the user typed too fast, the errors do not appear.

[hacknaked]

I've also noticed that using ngMessagesInclude can change the show/hide behavior in messages.

[longrunningprocess]

I've noticed the nodes for the messages are there but they have an opacity: 0 when it should be 1. Does this have something with ngAnimate?

[Clarity-89]

+1 wcjr I have the same issues.

[longrunningprocess]

I took a closer look at issue 6610 referenced by @grosem and it is fully explained there. Unfortunately it seems @ThomasBurleson labeled it for Q2 consideration :-( I noticed it was also labeled as an "Edge" case...that seems under-prioritized to me personally if I'm understanding the team's approach to solving this one.

[chadjaros]

+1
The required (number one) bug also seems to prevent other error messages (such as pattern) from showing up properly. Very annoying.

[longrunningprocess]

looks like these are related issues that are being worked now: 6859 and 6399

[topherfangio]

Hi all, we are indeed working on these issues; just trying to make sure we get some proper tests, and since this is related to animations, we're working with the core Angular team to make sure we have the proper approach. This is definitely a priority on our list!

[longrunningprocess]

Thanks for letting us know @topherfangio