Skip to content

fix(drag-drop): don't disable native drag interactions if dragging is disabled #14233

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

Merged
merged 1 commit into from
Dec 19, 2018

Conversation

crisbeto
Copy link
Member

Since consumers can use the cdkDragDisabled binding to disable dragging on an element, we shouldn't be disabling the native interactions unless we have to. These changes will only disable native interactions if dragging is enabled and there are no handles.

@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Nov 21, 2018
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 21, 2018
@crisbeto crisbeto force-pushed the drag-drop-disabled-interactions branch from a572687 to 18f19c9 Compare November 21, 2018 22:02
… disabled

Since consumers can use the `cdkDragDisabled` binding to disable dragging on an element, we shouldn't be disabling the native interactions unless we have to. These changes will only disable native interactions if dragging is enabled and there are no handles.
@crisbeto crisbeto force-pushed the drag-drop-disabled-interactions branch from 18f19c9 to 4e78404 Compare December 7, 2018 21:39
@jelbourn
Copy link
Member

I'm not sure about this one. The way I see it is that adding cdkDrag at all completely supersedes the native drag-drop, and disabling the directive just disables the directive's own behavior. Do you have a use case in mind where someone might want to alternate between cdkDrag and native drag on the same element?

@crisbeto
Copy link
Member Author

crisbeto commented Dec 14, 2018

By native drag&drop here I mean more the text selection etc. The intention behind the PR was to avoid doing things to people's styling unless we absolutely have to.

Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Dec 19, 2018
@jelbourn jelbourn merged commit 9fa3376 into angular:master Dec 19, 2018
josephperrott pushed a commit to josephperrott/components that referenced this pull request Jan 14, 2019
… disabled (angular#14233)

Since consumers can use the `cdkDragDisabled` binding to disable dragging on an element, we shouldn't be disabling the native interactions unless we have to. These changes will only disable native interactions if dragging is enabled and there are no handles.
@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 Sep 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants