Skip to content

Conversation

crisbeto
Copy link
Member

Fixes a regression after #30148 where we no longer detached the lazy content panel, causing its items to be retained until the next open when they get destroyed and re-created.

Fixes a regression after angular#30148 where we no longer detached the lazy content panel, causing its items to be retained until the next open when they get destroyed and re-created.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Jan 10, 2025
@crisbeto crisbeto requested a review from a team as a code owner January 10, 2025 08:01
@crisbeto crisbeto requested review from amysorto and andrewseguin and removed request for a team January 10, 2025 08:01
@crisbeto crisbeto added the G This is is related to a Google internal issue label Jan 10, 2025
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Jan 10, 2025
@crisbeto crisbeto merged commit 86a96c9 into angular:main Jan 10, 2025
27 checks passed
crisbeto added a commit that referenced this pull request Jan 10, 2025
Fixes a regression after #30148 where we no longer detached the lazy content panel, causing its items to be retained until the next open when they get destroyed and re-created.

(cherry picked from commit 86a96c9)
crisbeto added a commit that referenced this pull request Jan 10, 2025
Fixes a regression after #30148 where we no longer detached the lazy content panel, causing its items to be retained until the next open when they get destroyed and re-created.

(cherry picked from commit 86a96c9)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 10, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: material/menu G This is is related to a Google internal issue target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants