[Solved] Issue in Drag and Drop between ListView and Scheduler

[Augusto]

Hi. There is a problem when dragging an element from the list into the scheduler. The dropTarget element is not resolved correctly. The issue is more evident if the contents of the "kendo-draghint" are bigger.

The user expects to aim and drop using the cursor, but it seems kendo uses the center of kendo-draghint to resolve the dropTarget.

The issue is visible in the demo:

https://demos.telerik.com/kendo-angular-ui/demos/scheduler/editing/external-drag-and-drop

Thanks

[Martin Bechev]

Hi Augusto,

Thank you for the provided feedback.

I checked the demo, and it really has some room for improvement.

The problem was caused by how the drag-and-drop library resolves the "drop target" — it calculates which scheduler slot is under the drag hint by comparing the hint's full bounding rectangle against all registered drop zones and picking the one with the most overlap. When the hint element is large, its bounding box extends far beyond the cursor, so a completely different slot (often one below or to the right) would "win" the intersection check.

Here is the updated demo:

https://stackblitz.com/edit/angular-bs6edxnr

What was fixed:

Instead of relying on the hint's bounding rect, the code now reads originalEvent.target on every drag move. Because the hint has pointer-events: none, this always returns the exact DOM element physically under the cursor — the correct scheduler slot, regardless of hint size.

The drop zone <div> is now absolutely positioned (inset: 0) relative to its parent <td>, so the draggable area includes the cell padding. Before this change, hovering near the edge of a cell (in the padding area) would not register as a valid drop target.

Please check the demo and let me know if you have any follow-up questions.

Regards,
Martin Bechev
Progress Telerik