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.

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

fix(material/core): hide ripples inside drag&drop elements #29184

Merged
merged 1 commit into from
Jun 4, 2024

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Jun 4, 2024

When we create previews and placeholders for the drag&drop module, we clone the DOM node in its current state. This means that if there are ripples, they'll be in the clone as well.

These changes add a default styles to hide the ripple in such cases since it'll never disappear.

Fixes #29159.

When we create previews and placeholders for the drag&drop module, we clone the DOM node in its current state. This means that if there are ripples, they'll be in the clone as well.

These changes add a default styles to hide the ripple in such cases since it'll never disappear.

Fixes angular#29159.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Jun 4, 2024
@crisbeto crisbeto requested a review from devversion as a code owner June 4, 2024 07:51
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Jun 4, 2024
@crisbeto crisbeto merged commit c4a1407 into angular:main Jun 4, 2024
23 of 25 checks passed
crisbeto added a commit that referenced this pull request Jun 4, 2024
When we create previews and placeholders for the drag&drop module, we clone the DOM node in its current state. This means that if there are ripples, they'll be in the clone as well.

These changes add a default styles to hide the ripple in such cases since it'll never disappear.

Fixes #29159.

(cherry picked from commit c4a1407)
@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 Jul 5, 2024
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 target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug(matRipple): Ripple effect sometimes persists when used with cdkDrag
2 participants