Skip to content

fix(cdk/drag-drop): error if dragging starts from active sibling container #20704

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

Merged
merged 1 commit into from
Oct 16, 2020

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Oct 2, 2020

Currently we have a restriction that prevents users from starting a new drag sequence if an item within the same container is being dragged, however they can start one from a connected container and pull the item into the active one and start dragging it there. This can cause an error if it happens while the item's drop animation is running.

These changes add an extra check so that dragging can't be started out of a connected container either.

Relates to #20623.

…ainer

Currently we have a restriction that prevents users from starting a new drag sequence
if an item within the same container is being dragged, however they can start one
from a connected container and pull the item into the active one and start dragging
it there. This can cause an error if it happens while the item's drop animation is
running.

These changes add an extra check so that dragging can't be started out of a connected
container either.

Relates to angular#20623.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release labels Oct 2, 2020
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 2, 2020
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added the action: merge The PR is ready for merge by the caretaker label Oct 7, 2020
@annieyw annieyw merged commit 6d86f0f into angular:master Oct 16, 2020
annieyw pushed a commit that referenced this pull request Oct 16, 2020
…ainer (#20704)

Currently we have a restriction that prevents users from starting a new drag sequence
if an item within the same container is being dragged, however they can start one
from a connected container and pull the item into the active one and start dragging
it there. This can cause an error if it happens while the item's drop animation is
running.

These changes add an extra check so that dragging can't be started out of a connected
container either.

Relates to #20623.

(cherry picked from commit 6d86f0f)
@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 Nov 16, 2020
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 cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants