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

Nested drop targets do not work correctly. #17143

Closed
henrikdahl8240 opened this issue Sep 19, 2019 · 3 comments
Closed

Nested drop targets do not work correctly. #17143

henrikdahl8240 opened this issue Sep 19, 2019 · 3 comments

Comments

@henrikdahl8240
Copy link

Let's assume we take the example from the guide at https://material.angular.io/cdk/drag-drop/overview below the header "Transferring items between lists".

Here we have a div having the attribute [cdkDropListConnectedTo]="[todoList]".

We now do a very simple change, we edit that div and make a small hierarchy of drop targets by putting three divs inside each other, where they each have the attribute [cdkDropListConnectedTo]="[todoList]".

Now we should be able to drag items from the todoList and drop the items at any of the three divs making up the hierarchy.

Unfortunately it's always the outermost div which get's the drop and not the one below the mouse cursor. So, for example, if you drag an item from the todoList and release the mouse button above the innermost div, it's still the outer-most div, which gets the drop.

Shouldn't it rather be the div below the mouse pointer and not the outermost div?

I hope you may fix this, because it's rather difficult to drop at nodes in a hierarchy having the current behavior.

@henrikdahl8240
Copy link
Author

Perhaps this is actually the same problem: #17119

@mmalerba mmalerba added the needs triage This issue needs to be triaged by the team label May 20, 2020
@crisbeto crisbeto removed the needs triage This issue needs to be triaged by the team label Jul 12, 2020
@crisbeto
Copy link
Member

Duplicate of #16671.

@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 Aug 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants