md-input-container breaks route animations in angular 4.2.2

Bug, feature request, or proposal:

Bug

What is the expected behavior?

I implemented app with angular material and angular 4.2.2 route animation - as previewed here: https://github.com/matsko/ng4-animations-preview/blob/master/src/app/app.component.ts

Here is the code for animation:

animations: [
    trigger("routerAnimations", [
      transition("* <=> *", [
        query(':enter, :leave', style({ opacity: 1, transform: 'translateY(0)' }), { optional: true }),

        group([

          query(':enter', group([
            style({ opacity: 0, transform: 'translateY(10%)' }),
            animate('0.3s 320ms ease-in', style('*')),
            animateChild()
          ]), { optional: true }),

          query(':leave', group([
            animateChild(),
            animate('0.3s ease-out', style({ opacity: 0, transform: 'translateY(10%)' }))
          ]), { optional: true })

        ])
      ])
    ])
  ]

The router animations works as expected, unless there is <md-input-container> somewhere in a routed component. If there is this element, animation simply doesn’t run at all.

What is the current behavior?

There should be entry animation running, but animations are skipped entirely when <md-input-container> is present in routed component

What are the steps to reproduce?

See above

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

“@angular/material”: “^2.0.0-beta.6”, “@angular/animations”: “^4.2.2”

[mmalerba]

fix for this has been merged: https://github.com/angular/angular/pull/18210

[angular-automatic-lock-bot[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.}