Bug 51226 - Writer table EDITING: information lost while drag and drop
Summary: Writer table EDITING: information lost while drag and drop
Status: RESOLVED DUPLICATE of bug 32026
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
3.3.4 release
Hardware: All All
: medium critical
Assignee: Not Assigned
Depends on:
Reported: 2012-06-19 01:07 UTC by sasha.libreoffice
Modified: 2015-06-26 10:21 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description sasha.libreoffice 2012-06-19 01:07:14 UTC
Problem in Writer table that happens while drag and drop selected cells:
Steps to reproduce:
0. Start Writer
1. add table with one column and 4 rows
2. enter something to rows 2,3,4
3. select cells 2,3,4
4. drag and drop selected cells to cell 1
Expected: values appears in cells 1,2,3
Actually: value appear only in cell 1 (from cell 2), other are lost

Reproduced in 3.3.4, 3.5.4, 3.6 beta1 on Fedora 64 bit
and on 3.5.2 on Windows 7 32 bit

What is interesting: msWord 2007 behaves in such situation as expected
So, it done not for compatibility with Word

PS: when we press Ctrl-Z in Writer after step 4, Selected becomes only text in cells, not cells themselves. It will produce problem if we will try to drag and drop again. All values will appear in one cell.
Comment 1 bfoman (inactive) 2012-06-20 02:21:20 UTC
Confirmed with:
Build ID: own W7 debug build
Windows 7 Professional SP1 64 bit

Values missing in row 2 and 3. Ctrl-Z select text only.
Users migrating from Word 2010 could be surprised, as it behaves different.
Dragging rows down seems to work as expected.
Comment 2 Joel Madero 2013-02-07 17:29:16 UTC
Tested on: &
Version (Build ID: 027bb41aa16793e88e9fc1b3550c8c893363647)

Both worked for me. Marking as WFM. Sasha - if this is still an issue reopen it and I'll get someone to give a second opinion. Thanks
Comment 3 sasha.libreoffice 2013-02-08 05:56:20 UTC
reproduced in:
on RFR 17 64bit
Comment 4 Jorendc 2013-02-11 00:00:52 UTC
Thanks for reporting Sasha!

I can confirm this behavior using Mac OSX 10.8.2 and LibreOffice Version (Build ID: 042e4606a64233299fdc02d9df32329c452d96d)
TinderBox: MacOSX-Intel@3-OSX_10.6.0-gcc_4.0.1, Branch:master, Time: 2013-02-07_23:25:41

Following [1] I mark this as 'critical medium'.

[1] https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg
Comment 5 QA Administrators 2015-02-19 15:44:20 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice ( or later): https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

Thank you for your help!

-- The LibreOffice QA Team
This NEW Message was generated on: 2015-02-19
Comment 6 Buovjaga 2015-03-08 19:32:23 UTC

Win 7 Pro 64-bit, LibO Version:
Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432
Locale: fi_FI
Comment 7 Buovjaga 2015-06-26 10:21:33 UTC

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