The spec <https://www.w3.org/TR/css-ui-4/#propdef-user-select> is clear in this respect: none The UA must not allow selections to be started in this element. So, as a fix to this consider merging chromium patch: https://chromium.googlesource.com/chromium/src/+/f6dcdcf4917ba56f5576ef7d5d11d869630d2760 Test case from https://bugs.chromium.org/p/chromium/issues/detail?id=481985 > Open http://jsbin.com/zufeva/1/ > Start dragging on the first box (-webkit-user-select:none) and drag into the second (no -webkit-user-select). > IE and Firefox appear to implement their user-select variants differently where it controls whether selection can be STARTED. So there, if you start in the first box, you won't select text anywhere.
(In reply to Carlos Alberto Lopez Perez from comment #0) > > So, as a fix to this consider merging chromium patch: > https://chromium.googlesource.com/chromium/src/+/ > f6dcdcf4917ba56f5576ef7d5d11d869630d2760 > This fix can't be merged as such. It causes issues on the web-inspector, the text on the console becomes non selectable. The same happened on chromium after merging it (it was reverted later). See: https://bugs.chromium.org/p/chromium/issues/detail?id=615227
<rdar://problem/91955574>
Created attachment 457916 [details] Patch
The Web inspector issue is still reproducible.
STR for the WI issue: 1) Open DevTools, open Console 2) "window" and press enter 3) Try to select the logged text by clicking and dragging
This was the Chromium change that ended up getting merged: https://chromium-review.googlesource.com/c/chromium/src/+/570246/16/third_party/WebKit/Source/core/dom/Node.cpp along with: https://chromium.googlesource.com/chromium/src.git/+/d541129f1b272eb3e611b59b5e12dd0be0a4ba58