Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(material/core): ripple element not destroyed after trigger change #29012

Merged
merged 1 commit into from
May 9, 2024
Merged

fix(material/core): ripple element not destroyed after trigger change #29012

merged 1 commit into from
May 9, 2024

Conversation

enten
Copy link
Contributor

@enten enten commented May 7, 2024

Fix #29010

@enten enten requested a review from devversion as a code owner May 7, 2024 11:56
@devversion devversion requested review from wagnermaciel and crisbeto and removed request for devversion May 7, 2024 11:59
@crisbeto crisbeto removed the request for review from wagnermaciel May 8, 2024 11:43
@crisbeto crisbeto added action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release labels May 8, 2024
@crisbeto crisbeto self-assigned this May 8, 2024
@crisbeto crisbeto merged commit 8420471 into angular:main May 9, 2024
25 checks passed
crisbeto pushed a commit that referenced this pull request May 9, 2024
@enten @crisbeto
fix(material/core): ripple element not destroyed after trigger change (…
7a8e886 
…#29010) (#29012)

(cherry picked from commit 8420471)
crisbeto pushed a commit that referenced this pull request May 9, 2024
@enten @crisbeto
fix(material/core): ripple element not destroyed after trigger change (…
0b30688 
…#29010) (#29012)

(cherry picked from commit 8420471)
@Dzana-K Dzana-K mentioned this pull request Jun 6, 2024
Open
@ambrose40 ambrose40 mentioned this pull request Jun 6, 2024
Open
@Rosenstein Rosenstein mentioned this pull request Jun 6, 2024
Merged
@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 Jun 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@crisbeto crisbeto crisbeto approved these changes

Assignees

@crisbeto crisbeto

Labels
action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

bug(material/core): ripple element not destroyed after trigger change
2 participants
@enten @crisbeto