Bug 113085 - LibreOffice Writer Navigator: Ignores Drag Mode Settings, Won't Insert Copy
Summary: LibreOffice Writer Navigator: Ignores Drag Mode Settings, Won't Insert Copy
Status: RESOLVED DUPLICATE of bug 90661
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-13 01:12 UTC by MarjaE
Modified: 2017-10-13 21:38 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MarjaE 2017-10-13 01:12:31 UTC
Description:
When using the Navigator in LibreOffice Writer, to try to drag tables from one document to another, LibreOffice lists three drag modes: "Insert as Hyperlink," "Insert as Link," or "Insert as Copy."

Steps to Reproduce:
1. Open a writer document with a table. (I was trying to repair one table but got the same bug with other tables.)
2. Open the navigator.
3. Create a new writer document.
4. Right-click in the Nav and set the "Drag Mode" settings in the source document to "Insert as Copy."
5. Drag and drop from the Nav to the new writer document.

Actual Results:  
From one document, I get a link instead of the table.

From another document, I get a file path on my computer, without a link.

Expected Results:
I would expect to get the selected table.


Reproducible: Always

User Profile Reset: No

Additional Info:
I have encountered the bug, as described, in LibreOffice 5.4.0.3.

I have encountered a similar bug in NeoOffice, an OpenOffice derivative. I get a gray box instead of the table, or instead of a hyperlink, but get a link if I select the link option. This suggests a common origin in OpenOffice.


User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Firefox/52.0
Comment 1 Alex Thurgood 2017-10-13 11:01:45 UTC

*** This bug has been marked as a duplicate of bug 101072 ***
Comment 2 Cor Nouws 2017-10-13 21:38:35 UTC

*** This bug has been marked as a duplicate of bug 90661 ***