Change event on drag start (if delayed dragging, it should fire when the delay is elapsed)

[plchampigny]

Feature Description

Currently the started event on CdkDrag fires when the user starts to press on the element. Now with the dragStartDelay, it should fire after the delay if it hasn't been cancelled.

Use Case

I would like to trigger a vibration or a haptic feedback when the the dragged element starts to drag after the cdkDragStartDelay. Currently it's not possible to synchronize both of them accuratly without doing some hacks.

[plchampigny]

Related: #16537

This rework partially allow my feature to work, but the event should occur before the user actually starts to move.

(cdkDragStarted)="vibrate($event)"
[cdkDragStartDelay]="500"

This is the current behavior with these changes:

1. User press cdkDrag for 700 ms without moving
2. User starts to move
3. Device vibrate

This is the expected behavior:

1. User press cdkDrag for 500 ms without moving
2. Device vibrate after 500ms because drag is started
3. User starts to move (because he had the feedback that the element is dragging)

[williamxsp]

Any news with that feature? Id like to have the same behavior

[Marius-Romanus]

The same happens to me. It would be a very interesting functionality to warn the user that they can already move the card.

[angular-robot]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[angular-robot]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

[DavidMarquezF]

Is there any workaround for the moment?