mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
606de5166e
When a view has the `Dirty` flag and is reattached, we should ensure that it is reached and refreshed during the next change detection run from above. In addition, when a view is created and attached, we should ensure that it is reached and refreshed during change detection. This can happen if the view is created and attached outside a change run or when it is created and attached after its insertion view was already checked. In both cases, we should ensure that the view is reached and refreshed during either the current change detection or the next one (if change detection is not already running). We can achieve this by creating all views with the `Dirty` flag set. However, this does happen to be a breaking change in some scenarios. The one identified internally was actually depending on change detection _not_ running immediately because it relied on an input value that was set using `ngModel`. Because `ngModel` sets its value in a `Promise`, it is not available until the _next_ change detection cycle. Ensuring created views run in the current change change detection will result in different behavior in this case. Making option the default is the solution to #52928. That will have to wait for a major version. PR Close #53022 |
||
|---|---|---|
| .. | ||
| change_detection_integration_spec.ts | ||
| inheritance_integration_spec.ts | ||
| integration_spec.ts | ||
| ng_container_integration_spec.ts | ||
| ng_module_integration_spec.ts | ||
| projection_integration_spec.ts | ||
| query_integration_spec.ts | ||
| query_list_spec.ts | ||
| regression_integration_spec.ts | ||
| resource_loader_mock.ts | ||
| security_integration_spec.ts | ||
| source_map_integration_node_only_spec.ts | ||
| source_map_util.ts | ||
| view_injector_integration_spec.ts | ||