cdkDrag element prevents native drag interactions even when there is a drag handle

[atscott]

Bug, feature request, or proposal:

The cdkDrag element prevents native drag interactions even when there is a valid cdkDragHandle in that cdkDrag

What is the expected behavior?

When there is a cdkDragHandle inside a cdkDrag, native drag interactions are only disabled for the drag handle. If you can't drag without using the drag handle, I don't see why native drag interactions should be disabled on anything other than the drag handle.

What is the current behavior?

native drag interactions are disabled for the main cdkDrag and the drag handle

What are the steps to reproduce?

Providing a StackBlitz reproduction is the best way to share your issue.

StackBlitz starter: https://stackblitz.com/edit/angular-91ym56

Using an android phone or chrome dev tools device simulator and try to scroll down on the demo, using the box as a start position. You cannot scroll down, but I would have expected that you can unless you start the drag on the drag handle.

What is the use-case or motivation for changing an existing behavior?

On mobile, it is really hard to scroll the page when the cdkDrag element is large. A drag handle helps limit the drag/drop size so the user can still scroll when touching the cdkDrag element and not the cdkDragHandle.

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Reproduced on android chrome and desktop chrome device emulator (in developer tools). For whatever reason, this is not reproducible on iOS (which may indicate the native drag interactions are not being disabled correctly for iOS).

Is there anything else we should know?

[angular-automatic-lock-bot]

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.}