mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
06be8034bb
Previously, Angular would switch from the macrotask to a microtask scheduler _only_ when the scheduler was the trigger for the synchronization. This microtask scheduling is to ensure patterns such as `Promise.resolve().then(() => updateAppStateAgain())` _during_ synchronization are caught and synchronized again within the same event loop (guaranteeing that they aren't split across multiple browser paints). The microtask scheduler should be used after any tick, not just from those than run within the scheduler to always account for the promises within synchronization. This is encountered most frequently during bootstrap, which triggers the tick directly. In this change we exempt `TestBed.tick` and `ComponentFixture.detectChanges` from this behavior. Doing so would affect the timing of stability and tests are quite sensitive to this (e.g. `fixture.whenStable`). It is somewhat unfortunate that we have "special" test-only behavior. However, it is important to acknowledge that this only affects the test-only APIs as well. Any code in the application under test that triggers `ApplicationRef.tick` directly would still use the microtask scheduling behavior. fixes #65444 |
||
|---|---|---|
| .. | ||
| application_config.ts | ||
| application_init.ts | ||
| application_module.ts | ||
| application_ngmodule_factory_compiler.ts | ||
| application_ref.ts | ||
| application_tokens.ts | ||
| create_application.ts | ||
| platform_tokens.ts | ||
| tracing.ts | ||