New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor(cdk/overlay): Reduce dependency on NgZone #28332
Conversation
51b8b1b
to
017331a
Compare
blocked by angular/angular#52455 |
eagerly awaiting this now that the blocker is resolved, will it also fix the tooltip positioning in zoneless? |
yes, this would fix the tooltip positioning in Zoneless. Note that the focus right now is finalizing the Zoneless implementation. There’s still plenty of work that needs to be done there before downstream fixes like this start to get more dedicated time and attention. |
017331a
to
36d9780
Compare
36d9780
to
29652fa
Compare
This updates the overlay implementation to use `afterNextRender` instead of `ngZone.onStable` which does not emit at all in zoneless applications. For zone-based applications, this means that the overlay will be positioned immediately after the next ApplicationRef tick. This is slightly different from `onStable`, which with ZoneJS can span multiple change detection rounds.
4abdc4c
to
8cda325
Compare
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
draft - Probably a breaking change and definitely not a good idea until
afterNextRender
runs only afterApplicationRef.tick
. At the moment, this passes tests only because they're using fixtures and the fixtures are directly triggering change detection. However, in an application, the app component will refresh and triggerafterNextRender
before the overlay views are refreshed.