ng-content doesn't work with ng-container

[greenGoby]

Bug, feature request, or proposal:

When you have an ng-container, transclusion doesn't work

What is the expected behavior?

I would expect the selector of the transclusion to pull in the element

What is the current behavior?

The element is not selected for

What are the steps to reproduce?

http://plnkr.co/edit/NqAbVgUclJkOSQCrS97H?p=preview

What is the use-case or motivation for changing an existing behavior?

Found when putting md-error inside ng-container. md-input-field selector for md-error does not work
https://github.com/angular/material2/blob/9b4f4355bc89cb83295f10b8d1bea6ba3ab4d6d5/src/lib/form-field/form-field.html#L47

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Angular 5

Is there anything else we should know?

[willshowell]

Unfortunately, this is expected behavior in Angular. See #5263, #5292, and #6625.

[josephperrott]

Closing as duplicate of the issues above:

This is a consequence of how content project works; only the top-level elements inside the container are projected, so adding the intermediate container make it not work. Something to potentially file an issue on for Angular Core.

[greenGoby]

Sorry for that I actually meant to put that on the angular core one. Sounds like they are already aware though.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}