BrowserAnimationsModule breaks size calculations

🐞 bug report

Affected Package

@angular/platform-browser/animations

Is this a regression?

The latest version working was 5.2.3

Description

When Angular router is used to navigate and a new component is loaded into router-outlet, the size retrieved from the new compoent in OnInit or AfterViewInit is wrong whenever BrowserAnimationsModule is used.

In the StackBlitz example the FrameComponent gets loaded into router-outlet. In OnInit and AfterViewInit the size of the div #frame gets read by

this.frame.nativeElement.client[Width/Height]

When BrowserAnimationsModule is part of AppModule, the height of the div is completely wrong (should be the same as viewport height). If BrowserAnimationsModule does not get imported, the size of the div gets reported correctly.

This breaks any application that depends on size calculations.

🔬 Minimal Reproduction

https://stackblitz.com/edit/angular-rac6sy

• Load StackBlitz and open up the console (the sizes get logged there)
• Click on the link “Click Here”
• Check the logged size in the console (especially the height)
• Go to app.module and delete BrowserAnimationsModule from imports
• Reload and repeat the above process -> the size is now correct (viewport size)

🌍 Your Environment

Angular Version:

NG 9.0.6
Chrome 80.0.3987.132
Firefox 74
Windows 10 1909

Anything else relevant?

May be related to #20290 but I am not sure if it is the exact same problem

[FSDRE]

@jelbourn If I understand it correctly there is not really a solution for a simple task like “scrolling something into view after the page was rendered” without using zone-hacks or double change detection? Why is something basic like this not on a roadmap? And by “basic” I mean the feature, not the implementation, knowing it could be a lot of work.

“Working as expected” is weird. We have a pretty solid inconsistency here. Depending on what modules you include in the project, rendering changes completely and API’s suddenly return different values. I don’t know, it just doesn’t feel right. A framework should keep struggle away from the developers, not introduce confusion.

[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.}