bug(@angular/cdk/drag-drop): Grabbing a cdkDrag element with underlying link element cause the link to be grabbed with css transition

[Raphyyy]

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

When grabbing an element that just have been dropped, you will get the underlying link to be grabbed instead of the cdkDrag element if you drag from the link.
It only appears if used CSS transition on transform to make smoother moves, so I think the issue is happening when the CSS animation has not ended.
Attaching cdkDrag to a parent element instead of setting it on the element doesn't change a thing. (see difference between the "To do" cdkDropList and the "Done" cdkDropList.

Maybe related issue : https://stackoverflow.com/questions/68924215/cdkdrag-sometimes-grabs-uderlying-link-element

Note : the attached stackblitz run Angular 12.0.0, but the issue also appears on my local with Angular 13.2.2.

Reproduction

Steps to reproduce:

1. https://stackblitz.com/edit/angular-pqknrn-x92xnv?file=src/app/cdk-drag-drop-connected-sorting-group-example.html
2. Grab an element, drop it somewhere and quickly regrab-it from the link

Expected Behavior

The underlying link should not be dragged

Actual Behavior

The underlying link is dragged instead of the cdkDrag element

Environment

• Angular: 13.2.2
• CDK/Material: 13.2.2
• Browser(s): Chrome
• Operating System (e.g. Windows, macOS, Ubuntu): Windows 11

[Raphyyy]

It looks like the issue can also appears sometimes without having to drop and redrag the same item immediately.
Removing the css transition also seems to fix it

[Raphyyy]

There is a workaround : Simply add draggable="false" to the element to prevent the link from being dragged.
However, the cdk dragging still do not trigger when it happens.
Setting user-select: none do not fix it.

[crisbeto]

I couldn't quite reproduce the issue without slowing down the preview transition a lot, but my theory is that the dragging is actually happening on the placeholder element behind the preview. I have #24404 out to fix it, but can you double-check that adding the following CSS styles resolve the issue for you?

.cdk-drag-placeholder {
  pointer-events: none;
}

[Raphyyy]

Thanks @crisbeto, unfortunately this doesn't fix it on my side : https://stackblitz.com/edit/angular-pqknrn-x92xnv?file=src/app/cdk-drag-drop-connected-sorting-group-example.css

Adding this doesn't fix it neither :

.cdk-drag-placeholder * {
  pointer-events: none;
}

I kept the same 250ms transition. Did you try to quickly regrab the item before the transition end ?

[crisbeto]

Yes, I can't reproduce it at all with the 250ms transition on either Chrome or Firefox. I could reproduce it if I bump up the transition to 2500ms, but the pointer-events: none on the placeholder fixed it for me. The only other cause I can see is that by default we have some logic which makes it so that you have to drag at least 5px before dragging starts so that dragging isn't mistaken for clicking. You can try to reduce it by adding the following to the component:

providers: [{
  provide: CDK_DRAG_CONFIG,
  dragStartThreshold: 0
}]

[Raphyyy]

Added this to component :

  providers: [{
    provide: CDK_DRAG_CONFIG,
    useValue: {
      dragStartThreshold: 0
    } 
  }],

Doesn't fix it unfortunately. Tested the issue on another Windows 11 and got the same result (both in a clean environment browser)

[crisbeto]

I'm testing on a Windows machine as well so it's weird that it doesn't happen for me. One more thing worth trying is to expand the CSS from above to:

.cdk-drag-placeholder {
  pointer-events: none;
  touch-action: none;
  -webkit-user-drag: none;
  use-select: none;
}

This is what we set on other elements in order to prevent native dragging interactions.