Material: mdInputContainer: `ng-messages` errors are not shown alongside `md-checkbox`

[alexilyaev]

Related to: https://github.com/angular/material/issues/6767

Behavior:

• What is the issue?
  Errors in ng-messages are not shown when they are alongside md-checkbox
• What is the expected behavior?
  Should work just like with all other form elements.

CodePen to reproduce the issue:
http://codepen.io/alexilyaev/pen/YqJYgb?editors=1000

Angular Versions:

• Angular Version: 1.5.0
• Angular Material Version: 1.0.7

Additional Information:

• Browser Type: Chrome
• Browser Version: 50.0.2661.86 (64-bit)
• OS: Mac OS X 10.11.4

[brianfeister]

+1

[dougpix]

+1

[danidewitt]

+1

[destegabry]

+1

[crisbeto]

The message is actually still a part of the DOM, but it's not being animated in. This is a known issue. Take a look at #6399.

[alexilyaev]

@crisbeto It's not quite the same thing, in my case the message doesn't show up to begin with, and there's no such class name regarding the animation.

[sdesmond]

The Pen originally provided has a little bug. It's not including the ngMessages module, so even without the md-input-container, the message won't show. Here's an updated Pen:

http://codepen.io/anon/pen/qZGGgj?editors=1000

If you comment out md-input-container, the message shows as expected. If you leave it in, the message never shows.

[alexilyaev]

@sdesmond Thanks for catching that, I've updated my Pen.
So md-input-container still causes an issue.

[ThomasBurleson]

This issue is closed as part of our ‘Surge Focus on Material 2' efforts.
For details, see our forum posting @ http://bit.ly/1UhZyWs.

[alexilyaev]

@ThomasBurleson I don't get it, it's a legit bug, and I opened it with the provided guidelines.

I'm currently advocating to my colleagues and students to use Angular Material, and the reality is Angular 2 is not ready for production yet, and even when it will be, it will take a long time until most projects will get upgraded to it.
The Angular team clearly stated they will support Angular 1.x as long as there is considerable usage of it.

Why are you guys pushing off issues related to Angular Material 1.x?
It's an awesome library, and fun to work with, and is really making a good change in many companies.
Can't you get more people to work on it?