-
Notifications
You must be signed in to change notification settings - Fork 6.8k
bug(drag-drop): Safari selects text on drag #14403
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
Comments
This is most likely due to 1c74b03. We had to remove our previous workaround for Safari, because it had a lot of performance implications on pages with a lot of elements. |
Fixes being able to select text while dragging an item on Safari. Fixes angular#14403.
I also suspected that. Thanks for fixing it so fast :) |
Fixes being able to select text while dragging an item on Safari. Fixes angular#14403.
Fixes being able to select text while dragging an item on Safari. Fixes #14403.
…lar#14405) Fixes being able to select text while dragging an item on Safari. Fixes angular#14403.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
What is the expected behavior?
Safari (or any browser) should not select text when starting to drag an item.
What is the current behavior?
When starting to drag an item in a drop list, Safari selects the text that is near to the dragged item.
What are the steps to reproduce?
Stackblitz: https://stackblitz.com/edit/angular-material2-issue-b6tvka
Switch the versions of cdk and material to 7.1.0 to see the previous and correct behaviour.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?
I tried it with Chrome and Firefox on macOS and the bug did not appear there, so it is probably exclusive to Safari. This bug was introduced in the 7.1.1 release. Downgrading to 7.1.0 fixes this behaviour. This can easily be verified using the stackblitz example from above.
The text was updated successfully, but these errors were encountered: