I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

Currently, Angular animations crash if an unrecognized CSS property is encountered.

Expected behavior

Angular shouldn't crash on unrecognized CSS properties in animations, it should just ignore them.

Minimal reproduction of the problem with instructions

To reproduce create an animation using an unrecognized property. In my app using will-change broke Microsoft Edge; open this test case in Edge:
https://stackblitz.com/edit/angular-4mt9rf

What is the motivation / use case for changing the behavior?

Current animations behavior goes against a very nice CSS feature that unrecognized CSS declarations are simply ignored. It's also hard to animate new properties that are not implemented everywhere yet. It may also introduce random breakages to older browsers that would otherwise work fine.

Environment

Angular version: X.Y.Z


Browser: N/A
 
For Tooling issues:
- Node version: N/A
- Platform:  N/A

Others:
N/A