Created attachment 57775 [details]
A demonstration of the intended, and actual, behavior.
Steps to reproduce:
1) Create a table.
2) Merge some of the cells together so that the merged area is more than one column wide.
3) Select a different row in one of such columns.
4) Try to delete this column.
The only column deleted is the one actually chosen, like in LibreOffice Calc. The merged cell is intact, only combining one column less.
The only way to delete the merged cell is to have the merged cell itself selected(alternately: or the column the merged cell is originally from).
All the columns the merged cell combines are deleted, even if the selected cell is in a different row.
Tested on two different installations of LibreOffice 3.5.0 on Debian Squeeze amd64 and Ubuntu 10.04 LTS amd64.
[Reproducible] with "LibreOffice 3.3.4 - Ubuntu 11.04 (32bit) Spanish UI"
reproduced also in 3.5.2 on Windows 7 32 bit
Changing version to 3.3.4 as most early reproducible, due to comment 2
Created attachment 67608 [details]
Now I've reproduced this bug in LibreOffice 18.104.22.168 on Ubuntu 12.04 x64 and LibreOffice 22.214.171.124 on Archlinux x64.
*** Bug 48704 has been marked as a duplicate of this bug. ***
Changing Version: 3.3.3 due to downstream report https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564 .
** 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 (4.4.1 or later)
*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)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2015-04-01
Still REPRODUCIBLE with Version: 126.96.36.199
Build ID: c4c7d32d0d49397cad38d62472b0bc8acff48dd6
Hello to everybody. After read all the comments in this line, I have to inform than the bug still exist and It is not the only one problem, if in the design of the table, you merge all the cells of two column and finally two columns become in one column and you have to delete other column, this disapper too and only remind the columns than never has been merged at all.
The table need to handle the cells individually too, if you want to enlarge or short any single cell, you can't do it.
I've tested in LibreOffice 188.8.131.52 in Win 8.1 and Ubuntu 14.04 64 bits both.
@email@example.com: Please dont change version field if you dont know what it means (see also comment 6).
Setting version to 3.3.3 as it is the earliest affected (see comment 5).
*** Bug 96171 has been marked as a duplicate of this bug. ***
I noticed that if you try to delete a column that runs through a row that has been merged, that the whole table gets deleted.
Any sign of our intrepid heroes working on this?
This bug has really become a pain-in-the-neck. Any chance of getting it fixed in the next sub release?
Also present in 184.108.40.206.0.
Test case added where deleting middle column deletes table.
Work around, split spanning row to match columns, delete column, merge cells in row to span.
Created attachment 128063 [details]
Deleting middle column deletes table.
Bug present in 220.127.116.11
This was reported on 2012-02-28. This bug is an ABSOLUTE PAIN IN THE ASS !!! If you let it go any longer, you guys might as well change your names to Open Office. They NEVER fixed their bugs either.
Fix this NOW. Stop dragging your feet! FOUR YEARS IS LONG ENOUGH!
still an issue in 6.0
*** Bug 118111 has been marked as a duplicate of this bug. ***
*** Bug 118997 has been marked as a duplicate of this bug. ***
Reproducible with 18.104.22.168.alpha0+
it seems issue inhereted from OOo
*** Bug 124304 has been marked as a duplicate of this bug. ***
*** Bug 101091 has been marked as a duplicate of this bug. ***
There is some good discussion in the linked OOo bug report on this.
> For tables with merged cells, there are no columns or rows, there are only
> cells. When you select a few cells and click "delete row" or "delete column",
> you can't delete neither a row nor a column (there are no rows, no columns),
> you can either delete the whole table or merge the cells with right, left,
> upper or lower cells, by your choice, because each cell have a lot of adjacent
> cells. This gets really complicated.
(In reply to Justin L from comment #23)
> > cells. This gets really complicated.
What if we didn't bother with the complicated cases, only with the simple, well-structured ones? That's what users seem to care about, anyway. If someone's designing their floor tiles with Writer tables, deleting rows/columns is likely not part of their workflow ;).
(In reply to Aron Budea from comment #24)
> What if we didn't bother with the complicated cases
We already don't bother with the complicated case, that is why we have this bug report. This bug is complicated because it contains merged cells.
*** Bug 138602 has been marked as a duplicate of this bug. ***
The case is even more serious, since the attempt to only delete a column can delete the entire table:
The table has 3 columns and three rows.
I merge the cells of row #3.
In column 3, I select the cells in row #1 and row #2.
From the icons menus, I select Delete selected columns.
Result: My table is deleted.
Expected: The selected columns should be deleted, i.e. merged into a neighboring column.
Thus, after nine years, the original report by uls6502 can be confirmed 100%, although this is a rather serious bug.