skills/angular__angular
1
0
Fork 0
mirror of https://github.com/angular/angular.git synced 2026-09-14 13:54:52 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: add small clarification to ng-content (#57408)

Browse Source 
This expands the recommendation to avoid conditionally showing `<ng-content>` with additional context

PR Close #57408
This commit is contained in:
Jeremy Elbourn
2024-08-14 14:45:54 -07:00
committed by Dylan Hunn
parent 5537bf802f
commit 736c67bc15
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
adev/src/content/guide/components/content-projection.md
+5 -4
View File
@@ -66,11 +66,12 @@ template.
**The `<ng-content>` element is neither a component nor DOM element**. Instead, it is a special
placeholder that tells Angular where to render content. Angular's compiler processes
all `<ng-content>` elements at build-time. You cannot insert, remove, or modify `<ng-content>` at
run time. You cannot add **<span style="text-decoration:underline;">directives</span>**, styles, or
arbitrary attributes to `<ng-content>`.
run time. You cannot add directives, styles, or arbitrary attributes to `<ng-content>`.
You should not conditionally include `<ng-content>` with `ngIf`, `ngFor`, or `ngSwitch`. For
conditional rendering of component content, see [Template fragments](api/core/ng-template).
You should not conditionally include `<ng-content>` with `@if`, `@for`, or `@switch`. Angular always
instantiates and creates DOM nodes for content rendered to a `<ng-content>` placeholder, even if
that `<ng-content>` placeholder is hidden. For conditional rendering of component content,
see [Template fragments](api/core/ng-template).
## Multiple content placeholders