Issue Board : Drag and Drop breaks due to browser text selection
Summary
This is observed on Gitlab CE 8.12, with a client Google Chrome browser 53.0.2785.116 m on Win64.
I have recorded a video to make the issue easy to see, and perhaps this is "desired" behaviour, but as a user I find it highly undesirable. On the Issue board I want to click issues and I want to drag and drop and I don't want to select text and copy it to the clipboard.
video: https://www.youtube.com/watch?v=rHFsJhE4rMI&feature=youtu.be
This COULD be a bug/regression in Google Chrome, and not actually a bug in Gitlab CE's issue board, but we all know how this works at this point. It's annoying, reproduced for me every time on my gitlab CE instances.
Steps to reproduce
- If I mouse down anywhere inside the blank (non-text area), either towards the left or the right side of an issue on the issue board, and the mouse cursor is a drag cursor, I expect a drag to begin when I click the mouse.
- The behavior seems inconsistent, rendering it harder to use.
- When I try this in Firefox, everything works fine, and there is no inconsistency.
- When I use Chrome 53.0.x on my main workstation, which is my main daily-driver browser, this occurs.
- This occurs on my private internal Gitlab CEs and also on the main gitlab site (ie https://gitlab.com/warren.postma/gitlab-ci-multi-runner/board)
Expected behavior
I expect that any time I see a mouse drag cursor, a mouse down should result in a mouse drag drop action starting, not a browser text selection.
Actual behavior
Unwanted selection of text and inability to use drag and drop in the issue board.
Relevant logs and/or screenshots
video: https://www.youtube.com/watch?v=rHFsJhE4rMI&feature=youtu.be
Output of checks
Results of GitLab application Check
attached: check2check2.txt.txt (no errors)
Results of GitLab environment info
sudo gitlab-rake gitlab:env:info (info.txt attached) info.txt
Possible fixes
I suspect it's an css issue, where something that should have a no-selection style doesn't, or that it's actually a Chrome bug where it ignores no-selection style, or where the mighty Chrome devs have decided to require some new no-select css tag without telling anybody.