fa6cbb3ffe2e8de635901421a0411cbefd826c99
With Ivy, injecting a `ViewContainerRef` for a `<ng-container>` element results in two comments generated in the DOM. One comment as host element for the `ElementContainer` and one for the generated `LContainer` which is needed for the created `ViewContainerRef`. This is problematic as developers expect the same anchor element for the `LContainer` and the `ElementContainer` in order to be able to move the host element of `<ng-container>` without leaving the actual `LContainer` anchor element at the original location. This worked differently in View Engine and various applications might depend on the behavior where the `ViewContainerRef` shares the anchor comment node with the host comment node of the `<ng-container>`. For example `CdkTable` from `@angular/cdk` moves around the host element of a `<ng-container>` and also expects embedded views to be inserted next to the moved `<ng-container>` host element. See: https://github.com/angular/components/blob/f8be5329f8d94128ece5dfe3e8e998fe4077d44d/src/cdk/table/table.ts#L999-L1016 Resolves FW-1341 PR Close #30611
build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871)
Angular
Angular is a development platform for building mobile and desktop web applications using Typescript/JavaScript and other languages.
Quickstart
Changelog
Learn about the latest improvements.
Want to help?
Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues in the hotlist: community-help.