docs: document content projection limitations#68826
Merged
Merged
Conversation
JeanMeche
reviewed
May 20, 2026
Add a Limitations section to the content projection guide covering two common footguns that aren't obvious from the feature description alone. First, projected content lives in the declaring component's view, not the receiving component's. This means OnPush on the receiving component doesn't prevent projected content from being checked on every parent cycle, and projected content can't see the receiving component's viewProviders. Second, some library components (menus, tabs, lists) use ContentChildren to wire up keyboard navigation and ARIA behavior and assume they own their children directly. Projecting external content into them tends to break that behavior silently. Closes angular#49679
arturovt
force-pushed
the
docs/issue_49679
branch
from
96105fb to
75beeeb
Compare
JeanMeche
approved these changes
May 20, 2026
JeanMeche
added
action: merge
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a Limitations section to the content projection guide covering two common footguns that aren't obvious from the feature description alone.
First, projected content lives in the declaring component's view, not the receiving component's. This means OnPush on the receiving component doesn't prevent projected content from being checked on every parent cycle, and projected content can't see the receiving component's viewProviders.
Second, some library components (menus, tabs, lists) use ContentChildren to wire up keyboard navigation and ARIA behavior and assume they own their children directly. Projecting external content into them tends to break that behavior silently.
Closes #49679