Bug 100998 - Add an option in Writer Configuration to disable selected text drag'n'drop when editing
Summary: Add an option in Writer Configuration to disable selected text drag'n'drop wh...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.0.6.2 rc
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 118095 121226 (view as bug list)
Depends on:
Blocks: Drag-and-Drop
  Show dependency treegraph
 
Reported: 2016-07-19 01:24 UTC by Carl Gable Watts
Modified: 2023-10-19 09:38 UTC (History)
8 users (show)

See Also:
Crash report or crash signature:


Attachments
The option in MS Word 2016 (22.72 KB, image/png)
2020-02-16 09:25 UTC, Mike Kaganski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Carl Gable Watts 2016-07-19 01:24:23 UTC
There needs to be a way to disable "Text Drag'n'Drop" in Writer Configuration.

I find myself constantly accidentally drag'n'dropping the current text selection when I am actually trying to click to change the text selection.

This is a fundamental flaw in "text drag'n'drop". Microsoft Office has an option in it's configuration to disable it completely across all Microsoft Office apps.

I believe there was an option in the LibreOffice Configuration to do this at one time, which I used, but now that option seems to have been removed.

In the OpenOffice Bugzilla there is a bug report of the same problem.
Comment 1 Aron Budea 2016-07-19 03:48:02 UTC
The suggestion might be worth considering.
In the meantime, select with Alt key pressed, and it won't drag'n'drop.
Comment 2 Jean-Baptiste Faure 2016-08-24 04:56:12 UTC
Changed summary in enhancement proposition.
Valid enhancement request. Set to new. That does not mean it will implemented.

Best regards. JBF
Comment 3 lvm 2018-05-23 10:57:21 UTC
This definitely has my vote - accidental drag'n'drop is hugely annoying. Suggestion to use alt is not working - alt-click inside the selection does nothing, outside - creates a new selection without de-selecting the existing one.
Comment 4 Xisco Faulí 2018-11-07 11:19:35 UTC
*** Bug 118095 has been marked as a duplicate of this bug. ***
Comment 5 Xisco Faulí 2018-11-07 11:20:04 UTC
*** Bug 121226 has been marked as a duplicate of this bug. ***
Comment 6 Heiko Tietze 2018-11-07 11:30:22 UTC
My position in bug 118095 is WFM as drag 'n drop is standard behavior and the workaround is simple (c1). But if there is more agreement on the request I'm not opposing an option.
Comment 7 Thomas 2018-11-07 22:19:56 UTC
+1 to this as a feature, many people find drag-and-drop editing unintuitive, which is why it's an option in many word processors to disable it.
Comment 8 Heiko Tietze 2018-11-08 08:13:43 UTC
@Thomas: If you remove needsUXEval flag you should also remove libreoffice-ux-advice from the CC list (and vice versa of course). But I'd like to keep it for a while boiling here.
Comment 9 Mike Kaganski 2020-02-16 09:25:45 UTC
Created attachment 157916 [details]
The option in MS Word 2016

More requests:

https://ask.libreoffice.org/en/question/23072
https://ask.libreoffice.org/en/question/229601

Obviously this is an accessibility problem for some users.
Comment 10 Heiko Tietze 2020-02-19 08:41:28 UTC
Okay, so let's add this option.
Comment 11 Thomas Murphy 2021-11-12 00:42:46 UTC
Is this still a bug in the 7.2 release? If so we should bump the version this issue related to. +1 from me for this fix, drag and drop editing is super annoying for me, I turn it off on everything I can.
Comment 12 Mike Kaganski 2021-11-12 06:17:20 UTC
(In reply to Thomas Murphy from comment #11)
> Is this still a bug in the 7.2 release?

First of all, this is not a "bug", but enhancement request. Then yes, it is still not implemented in 7.2. There's no indication of resolution here: neither in whiteboard (telling you targets where changes have landed), nor in issue status (which would be "RESOLVED (CLOSED) FIXED").

> If so we should bump the version this issue related to.

No, you need to read the description of the field you refer to: it is labeled "Version: (earliest affected)", and has a tooltip telling that it's "The earliest version of the software in which the bug can be reproduced". I hope you don't do incorrect version changes right and left without careful study what the fields mean. Thanks for not doing it here, I appreciate that you only suggested this, not changed yourself.
Comment 13 peterjdelmonte 2022-01-28 21:10:58 UTC Comment hidden (me-too)
Comment 14 knecker 2023-10-19 09:38:22 UTC Comment hidden (me-too)